Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-4674

Enhance IPV6 documentation

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 6.x Doc Updates
    • None
    • None

    Description

      Current IPV6 documentation link for 6.0 is: 

      https://docs.couchbase.com/server/6.0/install/ipv6-setup.html

      After talking to customer, it looks like its inadquate in manner every for simple scenarios, like upgrading existing IPV4 clusters to IPv6.

       

      We need to add documentation for adding IPv6 to the cluster. Customer should be able to perform upgrades in rolling fashion (they should be able to fallback to IPv4).

       

      Say I have 3 nodes IPV4 cluster, and rebalance one node out, upgrade it to latest version of CB which supports IPv6, and add it back to the cluster. Now cluster has 2 nodes on IPv4 and one on IPv6. Means IPv6 nodes should be able to fallback on IPv4 to talk to other nodes and perform rest of the upgrades.

       

      Clear steps are needed to accomplish the task mentioned above.

       

       

      Attachments

        Issue Links

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

          Activity

            dfinlay Dave Finlay added a comment - - edited

            Ram Dhakne: on the issue of rolling upgrade. Rolling upgrade to IPv6 unfortunately isn't possible due primarily to limitations in Erlang. The cluster management nodes can only talk to each other via IPv6 or IPv4 - not both at the same time. This means it's necessary to shut the cluster down completely before moving to IPv6 and then restarting.

            However, we absolutely do need to update the docs to reflect the changes made in 5.5.3 to move away from static_config as the mechanism to enable IPv6. Docs team - please connect with Ajit Yagaty [X] on these changes.

            dfinlay Dave Finlay added a comment - - edited Ram Dhakne : on the issue of rolling upgrade. Rolling upgrade to IPv6 unfortunately isn't possible due primarily to limitations in Erlang. The cluster management nodes can only talk to each other via IPv6 or IPv4 - not both at the same time. This means it's necessary to shut the cluster down completely before moving to IPv6 and then restarting. However, we absolutely do need to update the docs to reflect the changes made in 5.5.3 to move away from static_config as the mechanism to enable IPv6. Docs team - please connect with Ajit Yagaty [X] on these changes.

            Re-assigning this to Ram Dhakne to determine whether there is anything in this ticket to document that is not already being requested in DOC-4689 and CBSE-6604.

            Dave said what is being requested in this is not supported. Unless this functionality is in development, this ticket should be closed.

            eric.schneider Eric Schneider (Inactive) added a comment - Re-assigning this to Ram Dhakne to determine whether there is anything in this ticket to document that is not already being requested in DOC-4689 and CBSE-6604. Dave said what is being requested in this is not supported. Unless this functionality is in development, this ticket should be closed.

            People

              ram.dhakne Ram Dhakne (Inactive)
              ram.dhakne Ram Dhakne (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty