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

user-assigned node name gets reset during cluster join, making hostname management usable only in "add server with this name" case

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.1.0
    • Fix Version/s: 2.1.1
    • Component/s: ns_server
    • Security Level: Public
    • Labels:

      Description

      SUBJ.

      See CBSE-619.

      This basically means hostname management not only does not work, but it's very much broken.

      Particularly there's no way to assign and keep 2.1.0 node's hostnames during rebalance upgrade path.

      Known workaround is doing:

      wget --post-data="ns_cluster:do_change_address(\"mysuperhostname.com\", true)." --user=Administrator --password=couchbase http://mysuperhostname:8091/diag/eval

      on 2.1.0 node after it's added but before it's rebalanced in.

      It is enough to do that only first time during rebalance upgrade. All subsequent nodes can be added via "Add Server" functionality where target server name is used as name to assign.

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          alkondratenko Aleksey Kondratenko (Inactive) added a comment -
          Show
          alkondratenko Aleksey Kondratenko (Inactive) added a comment - 2.1.1 backport is here http://review.couchbase.org/#/c/27518/
          Hide
          kzeller kzeller added a comment -

          Alk-

          Can you confirm if this needs any more documentation besides the release note? My understanding is this fix will bring the server functioning in a way that I already documented for hostnames.

          Karen

          Show
          kzeller kzeller added a comment - Alk- Can you confirm if this needs any more documentation besides the release note? My understanding is this fix will bring the server functioning in a way that I already documented for hostnames. Karen
          Hide
          alkondratenko Aleksey Kondratenko (Inactive) added a comment -

          correct. Confirming

          Show
          alkondratenko Aleksey Kondratenko (Inactive) added a comment - correct. Confirming
          Hide
          kzeller kzeller added a comment -

          Thanks!

          Show
          kzeller kzeller added a comment - Thanks!
          Hide
          larry Larry Liu [X] (Inactive) added a comment -

          Hi, Aleksey

          I performed some sanity test on Ubuntu32. Here are my steps:

          1. Installed 2 node cluster on version 2.0.1 with hostname hack
          2. Installed a new node with 2.1.1
          3. I added the new node to 2.0.1 cluster as hostname
          4. The node is added as ip.
          5. After rebalance, the node in the cluster shows as ip still.

          I am wondering if this is the correct steps to verify the issue.

          Larry

          Show
          larry Larry Liu [X] (Inactive) added a comment - Hi, Aleksey I performed some sanity test on Ubuntu32. Here are my steps: 1. Installed 2 node cluster on version 2.0.1 with hostname hack 2. Installed a new node with 2.1.1 3. I added the new node to 2.0.1 cluster as hostname 4. The node is added as ip. 5. After rebalance, the node in the cluster shows as ip still. I am wondering if this is the correct steps to verify the issue. Larry
          Hide
          alkondratenko Aleksey Kondratenko (Inactive) added a comment -

          You need to set 2.1.1's hostname first. You can do it on setup wizard. And this is most convenient place to join it to 2.0.1 cluster too

          Show
          alkondratenko Aleksey Kondratenko (Inactive) added a comment - You need to set 2.1.1's hostname first. You can do it on setup wizard. And this is most convenient place to join it to 2.0.1 cluster too
          Hide
          kzeller kzeller added a comment -

          Guys this is not at all what was communicated about this feature for 2.1. I was told from AliaskeyA as well as Bin that you 'can' set up hostname post-node-setup wizard in the 'add node' window only when you add the node to the cluster. It did not need to be established in the setup wizard first.

          Show
          kzeller kzeller added a comment - Guys this is not at all what was communicated about this feature for 2.1. I was told from AliaskeyA as well as Bin that you 'can' set up hostname post-node-setup wizard in the 'add node' window only when you add the node to the cluster. It did not need to be established in the setup wizard first.
          Hide
          larry Larry Liu [X] (Inactive) added a comment -

          Here is what I tried and I didn't see hostname issue.

          1. Installed 2 node cluster on version 2.0.1 with hostname hack
          2. Installed a new node with 2.1.1
          3. Open setup wizard in new node and set it up with hostname
          4. Join the cluster and the node is added as hostname.
          5. After rebalance, the node in the cluster shows as hostname.

          Larry

          Show
          larry Larry Liu [X] (Inactive) added a comment - Here is what I tried and I didn't see hostname issue. 1. Installed 2 node cluster on version 2.0.1 with hostname hack 2. Installed a new node with 2.1.1 3. Open setup wizard in new node and set it up with hostname 4. Join the cluster and the node is added as hostname. 5. After rebalance, the node in the cluster shows as hostname. Larry

            People

            • Assignee:
              iryna iryna
              Reporter:
              alkondratenko Aleksey Kondratenko (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes