Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Release Notes for Couchbase Server 7.0

    +

    Couchbase Server 7.0 introduces scopes and collections that provide new database organizaion structures within Couchbase. It also brings new capabilities to the Query Service in addition to support for scopes and collections.

    Take a look at What’s New? for a list of new features and improvements in this release.

    Release 7.0.0 (July 2021)

    Couchbase Server 7.0 was released in July 2021.

    Quick Links: Major Changes in Behavior from Previous Releases | New Supported Platforms | Known Issues | Fixed Issues | Common Vulnerabilities and Exposures

    Major Changes in Behavior from Previous Releases

    • With the introduction of scopes and collections, Couchbase Server stores documents in a collection, which are contained in a scope, which is in a bucket. A default scope and default collection is used when a named scope and collection is not available or has not yet been created. When you upgrade to version 7.0 from a previous version, your documents and indexes will be available in the default scope and default collection. The migration guide provides information on how to migrate your data from a previous version of Couchbase to take advantage of named scopes and collections.

      • Global secondary indexes need to be created for each collection.

    • Added support for out-of-order execution of operations in Data Service.

      When a Data Service request cannot be completed immediately, this enhancement enables looking ahead in the connection’s queue and starting work on the next request. Out-of-order execution behavior is enabled by default and you can choose to disable it. See Java SDK documentation for further information.

    • Global secondary indexes now supports concurrent creation of indexes.

    • The Internet Engineering Task Force (IETF) have formally deprecated both the TLS 1.0 and 1.1 protocols along with a wider industry movement to use newer, more secure standards. Keeping in line with these changes, we strongly recommend that clients which use TLS encryption use TLS 1.2 or higher, and have updated the default minimum TLS version for all Couchbase Server 7.0 clusters to TLS 1.2. Currently supported SDKs already support the TLS 1.2 standard, so in most cases no application changes are required.

      If you do need to configure the minimum TLS to a lower version (not recommended), follow the instructions provided in https://docs.couchbase.com/server/current/manage/manage-security/manage-tls.html#set-the-minimum-tls-version.

    • Updated license for Community Edition

      Couchbase Server comes in two editions: Enterprise Edition and Community Edition. You can find details on the differences between the two and licensing information on the Couchbase Server Editions page.

      • Enterprise Edition — The Enterprise Edition license provides for free for development and testing for Couchbase Enterprise Edition. A paid subscription for production deployment is required. Please refer to the pricing page for details on Couchbase’s Enterprise Edition.

      • Community Edition — The Community Edition license provides for free deployment of Couchbase Community Edition for departmental-scale deployments of up to five node clusters. It has recently been changed to disallow use of XDCR, which is now an exclusive Enterprise Edition feature.

    New Supported Platforms

    This release adds support for the following platforms:

    • macOS Big Sur for development only

    See Supported Platforms for the complete list of supported platforms.

    Deprecated Features and Platforms

    Deprecated and Removed Platforms

    The following platforms are deprecated and will be removed in a future release:

    • CentOS 8

    • macOS 10.14 (Mojave)

    • Microsoft Windows Server 2016

    The following platforms are removed and no longer available:

    • Ubuntu 16.04 LTS

    Deprecated and Removed Features

    • The 'cbdocloader' tool used to load sample datasets is deprecated in this release. You can use the 'cbimport' tool with the '--format sample' flag as the 'cbimport' tool provides an equivalent feature set and is collection-aware.

    • The MOSS index type, available in the full-text search service, is deprecated in this release.

    • Support for passwordless buckets,typically buckets from previously upgraded clusters (pre-5.x), is deprecated.

    • The old bucket sasl_password is deprecated in this release.

    • The search_query() function is deprecated. We recommend that you use Search() functions instead to run full text search queries directly within a N1QL query. Refer to https://blog.couchbase.com/n1ql-and-search-how-to-leverage-fts-index-in-n1ql-query/ for information on changing the syntax to leverage the Search() function.

    • View indexes in N1QL have been removed in this release.

    • The Data-Service histogram 'batch_read' has been removed. Use the existing 'bg_load' histogram instead to monitor background fetch durations.

    Known Issues

    This section highlights some of the known issues in this release.

    Analytics Service

    Issue Description

    MB-46646

    Summary: Quorum failover on a remote cluster requires manual intervention. Not performing these manual steps causes the results to vary based on which nodes the Analytics service is talking to, and the state of those nodes.

    Workaround: Following a quorum failover on a remote cluster, perform the following manual steps:

    1. Run DISCONNECT LINK if the remote link is still connected.

    2. Run ALTER LINK to update the link to point to a surviving node. This step is needed even if the previously specified host is still in the cluster as it resets the topology maintained in the metadata.

    3. Run CONNECT LINK to reconnect the link.

    MB-45996

    Summary: The Analytics service may run out of heap space when ingesting maximum size documents (20MB) with minimally-sized Analytics memory quota as some memory that is consumed during ingestion is not released until the link is disconnected.

    Workaround: Use smaller documents, increase the Analytics service memory quota, or disconnect the link before running queries to avoid this issue.

    MB-44849

    Summary: A Remote Collection that gets disconnected due to the loss of permissions is not reconnected if the permissions are re-established.

    Workaround: Re-establish the connection by running CONNECT LINK manually.

    Data Service

    Issue Description

    MB-47267

    Summary: Clusters with a large number of high capacity persistent buckets, delta node recovery may timeout, due to large persistent bucket’s warmup tasks being scheduled before the initial tasks of warmup for other buckets.

    Workaround: Increase the number of reader threads to reduce the likelihood of smaller bucket’s warmup tasks being delayed from running.

    MB-38978

    Summary: Under certain circumstances, such as running a cbcollect_info, requests may take longer than normal. Depending on the system workload and size, this may be even a few seconds, which can trigger the default timeout value from SDKs.

    Workaround: We recommend that you avoid gathering these stats or cbcollect_info during higher workload.

    Eventing Service

    Issue Description

    MB-45973

    Summary: After upgrading a cluster with a single Data node from version 6.6 to 7.0, Eventing timers are not triggered as expected after a swap rebalance to version 7.0. Note that this does not impact clusters with 2 or more data nodes, or when there are no deployed or paused Eventing Functions with timers.

    Workaround: Undeploy all Eventing Functions that use timers, or add a second Data node before upgrading to version 7.0 (which can be subsequently be removed after the upgrade is complete).

    MB-45785

    Summary: A race condition exists where an Eventing Function with a Feed Boundary set to "From now" sometimes ignores it’s checkpoint and resumes processing form Everything. This issue only impacts the UI and can occur when a user rapidly invokes pause, edit, or resume in succession.

    Workaround: The issue can be avoided by using the REST APIs to pause and resume Eventing Functions in production.

    Index Service

    Issue Description

    MB-46725

    Summary: In the case of an unsafe failover that removes one or more index nodes from the cluster, the Rebalance button on the UI may not be enabled even though some indexes or index partitions are not available because the remaining index node(s) did not have any of their replicas.

    Workaround: Issue a rebalance command via CLI couchbase-cli rebalance -c 127.0.0.1:8091 -u Administrator -p xxxxxx

    Query Service

    Issue Description

    MB-46876

    Summary: AT_PLUS queries do not work with collections when using scan_vectors.

    Views

    Issue Description

    MB-47094

    Summary: When request auditing is enabled in a Couchbase cluster, under very high Views query workload, the view-engine audit message queue may grow unbounded causing the view-engine to crash.

    Workaround: Disable auditing when Views are present in the cluster.

    Fixed Issues

    The Couchbase JIRA filter Couchbase Server 7.0.0 Notable Fixed Issues lists the notable issues fixed in this release. Note that you need to log in to Couchbase JIRA to be able to view the results of this JIRA filter.

    Common Vulnerabilities and Exposures

    See Couchbase Alerts for the complete list of common vulnerabilities and exposures.