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

[RN 2.0.1] ONGOING REPLICATIONS migrates to the cluster if the replication existed on the added server

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.1
    • Component/s: ns_server, XDCR
    • Security Level: Public
    • Labels:
      None
    • Flagged:
      Release Note

      Description

      cluster_run

      steps:
      1. cluster1: 127.0.0.1:9000,127.0.0.1:9000
      cluster2: 127.0.0.1:9002,127.0.0.1:9003
      2. unidirection replication of default bucket cluster1->cluster2
      3. remove 127.0.0.1:9000 from cluster1
      4. initialize 127.0.0.1:9000 and add 127.0.0.1:9001 to it

      so we expect to get that cluster1 is clean, but

      ONGOING REPLICATIONS on cluster1 contains:
      default this cluster bucket "default" on cluster "unknown" Replicating on change

      Server error during processing: ["web request failed",

      {path,"/pools/default/tasks"}

      ,

      {type,exit}

      ,
      {what,
      {noproc,
      {gen_server,call,
      [xdc_rdoc_replication_srv,

      {foreach_doc, #Fun<xdc_rdoc_replication_srv.2.131405864>}

      ,
      infinity]}}},
      {trace,
      [{gen_server,call,3,
      [

      {file,"gen_server.erl"}

      ,

      {line,188}

      ]},
      {xdc_rdoc_replication_srv,
      find_all_replication_docs,0,
      [

      {file,"src/xdc_rdoc_replication_srv.erl"}

      ,

      {line,194}

      ]},
      {ns_doctor,build_tasks_list,2,
      [

      {file,"src/ns_doctor.erl"}

      ,

      {line,174}

      ]},
      {menelaus_web,handle_tasks,2,
      [

      {file,"src/menelaus_web.erl"}, {line,1995}]},
      {menelaus_web,loop,3,
      [{file,"src/menelaus_web.erl"}

      ,

      {line,392}

      ]},
      {mochiweb_http,headers,5,
      [

      {file,"mochiweb_http.erl"}

      ,

      {line,136}

      ]},
      {proc_lib,init_p_do_apply,3,
      [

      {file,"proc_lib.erl"}

      ,

      {line,227}

      ]}]}] menelaus_web019 n_0@172.16.16.30 19:12:27 - Thu Feb 7, 2013

      # Subject Project Status CR V
      For Gerrit Dashboard: &For+MB-7706=message:MB-7706

        Activity

        Hide
        dipti Dipti Borkar added a comment -

        Let's discuss this first before merging. I want to make sure we have clear behavior defined.

        Show
        dipti Dipti Borkar added a comment - Let's discuss this first before merging. I want to make sure we have clear behavior defined.
        Hide
        Aliaksey Artamonau Aliaksey Artamonau added a comment -

        Actually the fix has been merged.

        Show
        Aliaksey Artamonau Aliaksey Artamonau added a comment - Actually the fix has been merged.
        Hide
        jin Jin Lim (Inactive) added a comment -

        OK, then we probably won't need to update release note nor understand error behavior. Aliaksey - if you have already verified this fix please mark it as resolved and assign it to Andrei for his verification. Thanks.

        Show
        jin Jin Lim (Inactive) added a comment - OK, then we probably won't need to update release note nor understand error behavior. Aliaksey - if you have already verified this fix please mark it as resolved and assign it to Andrei for his verification. Thanks.
        Hide
        dipti Dipti Borkar added a comment -

        synced with Alk about this. For completeness updating this bug with expected behavior.

        In general, when a node in "added" to a cluster (whether the cluster has 1 node or more) , the new node should be treated as a completely new node. No config from before the addition must remain. this includes replications , data buckets, view etc.

        Show
        dipti Dipti Borkar added a comment - synced with Alk about this. For completeness updating this bug with expected behavior. In general, when a node in "added" to a cluster (whether the cluster has 1 node or more) , the new node should be treated as a completely new node. No config from before the addition must remain. this includes replications , data buckets, view etc.
        Hide
        andreibaranouski Andrei Baranouski added a comment -

        it works fine with the latest dev code

        Show
        andreibaranouski Andrei Baranouski added a comment - it works fine with the latest dev code

          People

          • Assignee:
            andreibaranouski Andrei Baranouski
            Reporter:
            andreibaranouski Andrei Baranouski
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes