Couchbase Server

[RN 2.0.1] Error post upgrade: Cannot establish remote XDCR connection, fails with "case_clause,error"

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.1
  • Fix Version/s: 2.0.1
  • Component/s: documentation, ns_server
  • Security Level: Public
  • Environment:
    Online upgrade from 181 GA to 2.0GA
  • Flagged:
    Release Note

Description

Load 30 items on 181 2 node cluster.
Failover and rebalance out 1 181 node, and rebalance in a 2.0 node
Repeat for Failover and rebalance out 2nd 181 node, and rebalance in a 2.0 node

* Keep continuous sets/deletes on this cluster during rebalance/failovers.

New cluster now has all 2.0 nodes.

Setup a XDCR replication reference to another 2.0 node.

Cannot setup replication to another 2.0 node , reference replication fails with "case clause error"


Server error during processing: ["web request failed",
{path,"/pools/default/remoteClusters"},
{type,error},
{what,
{case_clause,
{error,
{case_clause,false},
[{ns_config,'-update_key/2-fun-0-',3},
{ns_config,handle_call,3},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]}}},
{trace,
[{menelaus_web_remote_clusters,
cas_remote_clusters,2},
{menelaus_web_remote_clusters,
do_handle_remote_clusters_post,4},
{menelaus_web,loop,3},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]}] (repeated 1 times)

Logs at
  1. File
    bug12.tar
    21/Jan/13 8:06 PM
    7.23 MB
    Ketaki Gangal

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Farshid Ghods added a comment -
per bug scrub -

Junyi could you look at this issue ?
Show
Farshid Ghods added a comment - per bug scrub - Junyi could you look at this issue ?
Hide
Permalink
Aliaksey Artamonau added a comment -
The cause has nothing to do with xdcr.
Show
Aliaksey Artamonau added a comment - The cause has nothing to do with xdcr.
Hide
Permalink
Aliaksey Artamonau added a comment -
Uploaded a fix: http://review.couchbase.org/24143. A workaround for 2.0 will be to restart the cluster.
Show
Aliaksey Artamonau added a comment - Uploaded a fix: http://review.couchbase.org/24143 . A workaround for 2.0 will be to restart the cluster.
Hide
Permalink
Aliaksey Artamonau added a comment -
merged
Show
Aliaksey Artamonau added a comment - merged
Hide
Permalink
Aliaksey Artamonau added a comment -
Farshid see my comment above about workaround that is needed for 2.0. This should probably be documented somewhere.
Show
Aliaksey Artamonau added a comment - Farshid see my comment above about workaround that is needed for 2.0. This should probably be documented somewhere.
Hide
Permalink
Farshid Ghods added a comment -
per Aliaksey A. comment it needs to be documented for release notes for 2.0.0 release
Show
Farshid Ghods added a comment - per Aliaksey A. comment it needs to be documented for release notes for 2.0.0 release
Hide
Permalink
Jin Lim added a comment -
This bug now tracks the release note requirement mentioned above. The code fix has been already merged and verified.
Show
Jin Lim added a comment - This bug now tracks the release note requirement mentioned above. The code fix has been already merged and verified.
Hide
Permalink
Karen Zeller added a comment -
If you can come by and give me an explanation of what happened, that would be great.
Show
Karen Zeller added a comment - If you can come by and give me an explanation of what happened, that would be great.
Hide
Permalink
Jin Lim added a comment -
Hi Karen, put some info here just in case we don't have a chance to sit and discuss.

This appears to be that it only occurs in 2.0. There is this bug that entries in the ns server dynamic config get purged when a 2.0 node. This unfortunately causes the failure in establishing connection to remote XDCR cluster from the 2.0. node. \

The fix has merged into 2.0.1 and if any reason a user happens to be on 2.0.0 the workaround is to restart the failed node again after running into the error.

Hope this helps,
Jin
Show
Jin Lim added a comment - Hi Karen, put some info here just in case we don't have a chance to sit and discuss. This appears to be that it only occurs in 2.0. There is this bug that entries in the ns server dynamic config get purged when a 2.0 node. This unfortunately causes the failure in establishing connection to remote XDCR cluster from the 2.0. node. \ The fix has merged into 2.0.1 and if any reason a user happens to be on 2.0.0 the workaround is to restart the failed node again after running into the error. Hope this helps, Jin
Hide
Permalink
Karen Zeller added a comment -
Added to 2.0.1 RN:

In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the
dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster
references to be lost on the 2.0 nodes. This is now fixed.
Show
Karen Zeller added a comment - Added to 2.0.1 RN: In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster references to be lost on the 2.0 nodes. This is now fixed.
Hide
Permalink
Karen Zeller added a comment -
Added to 2.0.1 RN:

In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the
dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster
references to be lost on the 2.0 nodes. This is now fixed.
Show
Karen Zeller added a comment - Added to 2.0.1 RN: In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster references to be lost on the 2.0 nodes. This is now fixed.

People

  • Assignee:
    Karen Zeller
    Reporter:
    Ketaki Gangal
Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: