Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-7568

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

    Details

    • 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. bug12.tar
        7.23 MB
        Ketaki Gangal
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        jin 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 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
        kzeller kzeller added a comment -

        If you can come by and give me an explanation of what happened, that would be great.

        Show
        kzeller kzeller added a comment - If you can come by and give me an explanation of what happened, that would be great.
        Hide
        jin 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 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
        kzeller kzeller 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
        kzeller kzeller 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
        kzeller kzeller 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
        kzeller kzeller 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:
            kzeller kzeller
            Reporter:
            ketaki Ketaki Gangal
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes