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

[2.0.2 RN + Manual?]Host name and IP address management in Couchbase

    Details

    • Flagged:
      Release Note

      Description

      • Need ability to use host names that don't revert to IPs
      • Need ability to non-disruptively change the IP address of nodes
      • When setting up hostname based cluster(using etc/hosts), nodes revert back to ip when a new node is added by Hostname.

      From logs:

      Decided to change address to "<IP>"

      Steps followed:
      1.) Install 2.0 GA
      2.) Stop couchbase-server
      3.) Add ns_name to couchbase-server
      4.) remove files per:http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html
      5.) add hostname to /opt/couchbase/var/lib/couchbase/ip
      6.) Start server and configure with beer-sample
      7.) Hostname shows up correctly
      8.) Add new node by hostname(no need to rebalance)

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

        Activity

        Hide
        maria Maria McDuff (Inactive) added a comment -

        Shashank has tested this feature. The test cases for EC2 were executed and the status for those are updated in the test plan:
        http://hub.internal.couchbase.com/confluence/display/QA/Hostname+Management+Test+Plan

        A couple of points to note here are:

        • The private IP of EC2 instances don't get changed on reboot. So that particular case couldn't be verified. However, after reboot couchbase works fine in EC2(with hostnames). [Test 22,23]
        • On stopping/starting an instance, both hostname/ip change and the already installed couchbase server stops working. This looks ok to me. [Test 46,47]

        Shashank was talking to Ketaki on this. If we want to test changing the IP while hostname remains the same or vice-versa, we'll need ITs help to setup something special internally for this.

        Thanks,
        Deep

        Show
        maria Maria McDuff (Inactive) added a comment - Shashank has tested this feature. The test cases for EC2 were executed and the status for those are updated in the test plan: http://hub.internal.couchbase.com/confluence/display/QA/Hostname+Management+Test+Plan A couple of points to note here are: The private IP of EC2 instances don't get changed on reboot. So that particular case couldn't be verified. However, after reboot couchbase works fine in EC2(with hostnames). [Test 22,23] On stopping/starting an instance, both hostname/ip change and the already installed couchbase server stops working. This looks ok to me. [Test 46,47] Shashank was talking to Ketaki on this. If we want to test changing the IP while hostname remains the same or vice-versa, we'll need ITs help to setup something special internally for this. Thanks, Deep
        Hide
        dipti Dipti Borkar added a comment -

        Needs to go into the new behavior section of the release notes.

        Show
        dipti Dipti Borkar added a comment - Needs to go into the new behavior section of the release notes.
        Hide
        maria Maria McDuff (Inactive) added a comment -

        Deep –

        Scenarios to confirm:
        AWS: After upgrade, verify that the host is reachable by hostname (DNS resolution) even if private IP in amazon changed
        AWS: After restart of instance, verify same as above.

        Thanks,
        Maria

        Show
        maria Maria McDuff (Inactive) added a comment - Deep – Scenarios to confirm: AWS: After upgrade, verify that the host is reachable by hostname (DNS resolution) even if private IP in amazon changed AWS: After restart of instance, verify same as above. Thanks, Maria
        Hide
        deepkaran.salooja Deepkaran Salooja added a comment -

        Following CBQE tasks have been created to verify this change:

        CBQE-1209
        CBQE-1214
        CBQE-1215
        CBQE-1221

        Show
        deepkaran.salooja Deepkaran Salooja added a comment - Following CBQE tasks have been created to verify this change: CBQE-1209 CBQE-1214 CBQE-1215 CBQE-1221
        Hide
        kzeller kzeller added a comment -

        Input via email:

        Hi Karen,

        Fwding you information from Aliaksey on the recent changes.

        Will add notes on the ticket, once tested and verified.

        thanks,
        Ketaki

        Begin forwarded message:

        From: Aliaksey <alkondratenko@gmail.com>
        Subject: Re: Ref: Need more information - MB-7398 (Hostname Management)
        Date: April 11, 2013 10:11:51 AM PDT
        To: Ketaki Gangal <Ketaki@couchbase.com>
        Cc: Deepkaran Salooja <deepkaran.salooja@globallogic.com>

        2.0.0 way is forbidden since 2.0.1. I don't know if that's documented or not but it must be.

        2.0.1 instructions are actually compatible with new code. But manual change of address is not recommended anymore.

        On Wed, Apr 10, 2013 at 7:28 PM, Ketaki Gangal <Ketaki@couchbase.com> wrote:
        Hi Aliaksey,

        For testing changes from MB-7398 (Hostname Management), is http://review.couchbase.org/#/c/25463/3/CHANGES the right place to look for usage?

        Does this also mean, the older way http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html is/not valid anymore?

        Could you confirm?

        thanks,
        Ketaki

        On Apr 10, 2013, at 6:50 PM, Deepkaran Salooja wrote:

        Hi Maria,

        For the changes done related to MB-7398 (Hostname Management), I think I need more information on what changes have been done. Is there any specs or documentation that you are aware of related to this?
        And also need to find out if our earlier mechanism of hostname configuration is still valid:
        http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html

        Thanks,
        Deep

        Show
        kzeller kzeller added a comment - Input via email: Hi Karen, Fwding you information from Aliaksey on the recent changes. Will add notes on the ticket, once tested and verified. thanks, Ketaki Begin forwarded message: From: Aliaksey <alkondratenko@gmail.com> Subject: Re: Ref: Need more information - MB-7398 (Hostname Management) Date: April 11, 2013 10:11:51 AM PDT To: Ketaki Gangal <Ketaki@couchbase.com> Cc: Deepkaran Salooja <deepkaran.salooja@globallogic.com> 2.0.0 way is forbidden since 2.0.1. I don't know if that's documented or not but it must be. 2.0.1 instructions are actually compatible with new code. But manual change of address is not recommended anymore. On Wed, Apr 10, 2013 at 7:28 PM, Ketaki Gangal <Ketaki@couchbase.com> wrote: Hi Aliaksey, For testing changes from MB-7398 (Hostname Management), is http://review.couchbase.org/#/c/25463/3/CHANGES the right place to look for usage? Does this also mean, the older way http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html is/not valid anymore? Could you confirm? thanks, Ketaki On Apr 10, 2013, at 6:50 PM, Deepkaran Salooja wrote: Hi Maria, For the changes done related to MB-7398 (Hostname Management), I think I need more information on what changes have been done. Is there any specs or documentation that you are aware of related to this? And also need to find out if our earlier mechanism of hostname configuration is still valid: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-bestpractice-cloud-ip.html Thanks, Deep

          People

          • Assignee:
            mikew Mike Wiederhold
            Reporter:
            james.mauss James Mauss
          • Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes