A newer version of this documentation is available.

View Latest

Upgrading to Couchbase Server 6.0

    +

    Upgrading to the latest version of Couchbase Server allows you to leverage the latest features and helps keep your cluster running well. The following table summarizes the new features in this release, and describes what parts of the cluster need to be upgraded to enable them.

    Table 1. Couchbase Server 6.0 Feature Upgrade Matrix
    Feature Upgrade Level Upgrade Type Upgrade Path Mixed Mode Dependencies

    Analytics Service

    Cluster

    Offline/Online

    Direct

    No

    Analytics data from Developer Preview releases cannot be upgraded.

    If you plan to use the production release of Couchbase Analytics in version 6.0, you must perform a fresh installation of Couchbase Server 6.0 on any existing Analytics nodes that are running a previous version; otherwise, the Analytics Service will not function properly.

    Timers (Eventing Service)

    Cluster

    Offline/Online

    Direct

    No

    All Eventing nodes must be running version 6.0 to enable this feature.

    Scorch indexing system (Search Service)

    Cluster

    Offline/Online

    Direct

    Yes*

    *After upgrading to Couchbase Server 6.0, existing Full Text Indexes will continue to use the Moss index type, while new Full Text Indexes will use the Scorch index type by default. These Moss indexes can be upgraded to Scorch by updating their respective definitions with the new index type.

    Note that existing indexes that do not have indexType explicitly specified in the index definition are considered to use the default index type. These indexes will continue to use the Moss index type after upgrading to Couchbase Server 6.0. However, any further updates to the index definition will result in the index being upgraded to Scorch. Indexes created through the Couchbase Web Console automatically include the index type, therefore this issue only applies to indexes that were created using the command line.

    Mixed Mode in this context refers to only the nodes that are running the indicated service. So if 'No' is marked in the Mixed Mode column of a given feature, then all of the cluster nodes that are running that service must be upgraded to Couchbase Server 6.0 in order to enable that feature. If 'Yes', then the feature can potentially be enabled even if some of the nodes that are running the indicated service are on older versions of Couchbase Server

    Migrating Data from an IPv4 Cluster to an IPv6 Cluster

    You can migrate data from an IPv4 cluster to an IPv6 cluster with an offline upgrade, or online by using unilateral replication. You must ensure that your operating system has dual stack support.

    Offline Upgrade from an IPv4 Cluster to an IPv6 Cluster

    Prerequisites:
    • Ensure that the source cluster is on an operating system with dual stack support.

    Steps:
    1. Follow the instructions for performing an offline upgrade.

    2. When all the nodes are offline, restart each node with IPv6 enabled according to the IPv6 setup instructions.

    Online Upgrade from an IPv4 Cluster to an IPv6 Cluster using XDCR

    Prerequisites:
    • Ensure that the source cluster is running Couchbase Server 5.5 or newer on an operating system with dual stack support.

    • Ensure that the destination cluster is running Couchbase Server 5.5 or newer on an IPv6 network.

    Steps:
    1. Upgrade the source cluster to Couchbase Server 5.5 or newer.

    2. Create a new cluster with IPv6 enabled and configured according to the IPv6 setup instructions.

      This cluster needs to be sized appropriately for the workload, but does not need to be identical to the source cluster.

    3. Create a cluster reference and replication stream from the source to the destination cluster.

      At this point, the destination cluster is not receiving any application load directly, other than the replication traffic from the source cluster.

    4. Monitor the XDCR queue from the source until all mutations are replicated to the destination cluster.

    5. Reconfigure the application to start accessing the destination cluster.

    6. Once all of your applications have been moved, you can decommission the source cluster.

    IPv4 and IPv6 clusters cannot be paired for bi-directional (active-active) XDCR replication. For bi-directional replication, both clusters need to be using IPv4 or IPv6.