diff --git a/modules/learn/pages/clusters-and-availability/removal.adoc b/modules/learn/pages/clusters-and-availability/removal.adoc index eb0d338d89..8e9419978c 100644 --- a/modules/learn/pages/clusters-and-availability/removal.adoc +++ b/modules/learn/pages/clusters-and-availability/removal.adoc @@ -14,7 +14,7 @@ However, removal should be used only when all nodes in the cluster are responsiv Removal essentially means using xref:learn:clusters-and-availability/rebalance.adoc[Rebalance] to redistribute data across a subset of pre-existing cluster-nodes. It can be performed with the UI, the CLI, or the REST API. When the CLI or REST API is used, a single command initiates a rebalance, specifying which nodes are to be excluded. -When the UI is used, nodes to be removed are first identified, then rebalance is initiated. +When the UI is used, nodes to be removed are first identified; then rebalance is initiated. When the rebalance is complete, the _cluster map_ is correspondingly updated and distributed to clients. The process occurs while the cluster continues to service requests for data. @@ -74,7 +74,7 @@ As Table 1 shows, each of the four nodes takes a roughly equal share of the buck It also takes a roughly equal share of the replica bucket-items, kept in _replica_ vBuckets. Since the bucket has two replicas, the ratio of _active_ to _replica_ items, both on each node and in the total for the cluster, is approximately _1:2_. -Table 2 shows the results on the cluster of the removal of node 4 and subsequent rebalance. +Table 2 shows the results on the cluster when node 4 is removed and the cluster is rebalanced. .Three Surviving Data Service Nodes, One Bucket with 31,591 Items, Two Replicas [cols="2,3,3"] @@ -147,9 +147,25 @@ Note that since multiple buckets may have been configured, and different replica For further examples of rebalance, in the context of _failover_, see xref:learn:clusters-and-availability/failover.adoc[Failover]. +=== Changing the IP address of a node + +If you are changing the IP address of a node: + +. Remove the node from the cluster. +. Stop the server. +. Remove all the configuration files for the cluster affected by the IP change. The configuration files are located in `/opt/couchbase`. To delete the files, run the terminal command: ++ +[source, shell] +---- +rm -r /opt/couchbase +---- + +. Restart the server. +. Add the node with the changed IP address back into the cluster. + [#removal-versus-graceful-failover] == Removal versus Graceful Failover As an alternative to removal, a responsive Data Service node can be taken out of a cluster by means of _Graceful Failover_. -This may be faster, but the consequences do not maintain previous availability-levels. +This may be faster, but the consequences do not maintain previous availability levels. An account of the advantages and disadvantages is provided in xref:learn:clusters-and-availability/graceful-failover.adoc#advantages-and-disadvantages[Graceful Failover]. diff --git a/modules/release-notes/pages/relnotes.adoc b/modules/release-notes/pages/relnotes.adoc index e6a08f3389..18887b8a17 100644 --- a/modules/release-notes/pages/relnotes.adoc +++ b/modules/release-notes/pages/relnotes.adoc @@ -9,6 +9,7 @@ These release notes are focused on bug fixes and breaking changes. For information about new features and major improvements made in Couchbase Server 8.0, see xref:introduction:whats-new.adoc[What's New]. +include::partial$docs-server-8.0.1-fixes-and-improvements.adoc[] include::partial$docs-server-8.0.0-fixes-and-improvements.adoc[] include::partial$docs-server-8.0.0-breaking-changes.adoc[] include::partial$docs-server-8.0.0-known-issues.adoc[] diff --git a/modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc b/modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc new file mode 100644 index 0000000000..3562c4afa7 --- /dev/null +++ b/modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc @@ -0,0 +1,162 @@ + + + +[#release-801] +== Release 8.0.1 (March 2026) + +Couchbase Server 8.0.1 was released in March 2026. +This maintenance release contains fixes to issues. + +[#dlist-fixed-issues-801] +== Fixed Issues + + + + +[#dlist-fixed-issues-801-cluster-manager] +=== Cluster Manager + +*https://jira.issues.couchbase.com/browse/MB-69026/[MB-69026]*:: + +Addressed an issue with stuck rebalance email alerts in Couchbase Server. + +This fix resolves problems observed when "Require encryption (TLS)" was configured, +causing alert failures. + +*https://jira.issues.couchbase.com/browse/MB-69650/[MB-69650]*:: + +A problem was introduced in 7.6.2 where the presence of a Cloud Native Gateway in the cluster would cause issues for services connecting to the cluster manager. + +The presence of Cloud Native Gateway no longer causes these issues. + +*https://jira.issues.couchbase.com/browse/MB-70441/[MB-70441]*:: + +The upgrade to Erlang version 26 introduced a change in behavior which requires peer certification when TLS is being used for Alert emails. +The peer certification introduced with the changes for this ticket uses the trusted CA certificates provided by the operating system. + + + + + + + + + +[#dlist-fixed-issues-801-query-service] +=== Query Service + +*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*:: + +* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries. +This has been addressed by denying the sargability for such indexes. +* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes. +* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed. + +*https://jira.issues.couchbase.com/browse/MB-69081/[MB-69081]*:: + +To retrieve a document's expiration, +the user had to specify the sub-path explicitly, +i.e `META().expiration`. +A call to the `META()` function without the sub-path would return the default expiration value 0 always which was incorrect. + + +Now, +when a user’s query invokes META() function without explicitly specifying the sub-path the document's expiration value is returned. + +*https://jira.issues.couchbase.com/browse/MB-69083/[MB-69083]*:: + +Problem: + +A query may return an incorrect result under the following conditions: + +* query contains one or more joins +* one of the joins involves a sub-query (FROM clause subquery) +* the FROM clause sub-query has a GROUP BY and/or aggregates +* the FROM clause sub-query can take advantage of index group/aggregate pushdown +(this requires an appropriate secondary index) +* CBO is ON, +and UPDATE STATISTICS has been run on all keyspaces/indexes involved + +*https://jira.issues.couchbase.com/browse/MB-69955/[MB-69955]*:: + +`CYCLE` was added as a KEYWORD for RECURSIVE WITH’s CYCLE sub-clause. + +This causes a syntax error when a path or sub-path’s case-insensitive identifier is named `cycle` when users upgraded to a version that supported the recursive with feature https://docs.couchbase.com/server/current/n1ql/n1ql-language-reference/with-recursive.html[WITH recursive clause] + +This is now handled by allowing `cycle` keyword as a permitted identifier. + +*https://jira.issues.couchbase.com/browse/MB-70112/[MB-70112]*:: + +When a prepared request is made with the `auto_execute` request parameter set as `true`, +the request would incorrectly error out with error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement` + +In this release the server silently ignores the `auto_execute` request parameter when the request is a prepared request. + + + + + + + +[#dlist-fixed-issues-801-index-service] +=== Index Service + +*https://jira.issues.couchbase.com/browse/MB-69935/[MB-69935]*:: + +Updated chronology for certain storage API calls to avoid rare corner case of shard metadata mismatch. + + + +[#dlist-fixed-issues-801-search-service] +=== Search Service + +*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*:: + +* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries. +This has been addressed by denying the sargability for such indexes. +* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes. +* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed. + + + +[#dlist-fixed-issues-801-tools] +=== Tools + +*https://jira.issues.couchbase.com/browse/MB-67774/[MB-67774]*:: + +Support has been added for Debian 13 (Trixie). +This update expands compatibility to include the latest Debian operating system. +Our systems have undergone testing to confirm full functionality on this new platform. +Stable performance has been verified through comprehensive evaluations. +We are committed to supporting a broader range of operating environments. + +// generated by gemini:gemini-2.5-flash + + + +*https://jira.issues.couchbase.com/browse/MB-70235/[MB-70235]*:: + +In 8.0.0 restoring to a 7.6 and below cluster with `--auto-create-buckets` did not work as we were sending a new setting. +We now omit the setting depending on the version. + +*https://jira.issues.couchbase.com/browse/MB-70255/[MB-70255]*:: + +Fixes bug where buckets with cross-cluster versioning enabled (link:https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-enable-crossclusterversioning.html[XDCR enable cross cluster versioning] ) would cause a merge to fail + + + +[#dlist-fixed-issues-801-uncategorized] +=== Uncategorized + +*https://jira.issues.couchbase.com/browse/MB-67774/[MB-67774]*:: + +Support has been added for Debian 13 (Trixie). +This update expands compatibility to include the latest Debian operating system. +Our systems have undergone testing to confirm full functionality on this new platform. +Stable performance has been verified through comprehensive evaluations. +We are committed to supporting a broader range of operating environments. + +// generated by gemini:gemini-2.5-flash + + +