Skip to content

Commit e030140

Browse files
authored
Merge pull request #3847
* [DOC-13459]: Create release note for Couchbase Server 7.6.8 * [DOC-13459]: Create release note for Couchbase Server 7.6.8 * [DOC-13459]: Create release note for Couchbase Server 7.6.8 * [DOC-13459]: Updated 7.6.8 release notes with fixes, date adjustment,… * [DOC-13459]: Updated 7.6.8 release notes to refine Magma configuratio… * [DOC-13459]: Revised 7.6.8 release notes with updated issue tables an… * [DOC-13459]: Revised 7.6.8 release notes with updated issue tables an…
1 parent a69eab6 commit e030140

3 files changed

Lines changed: 152 additions & 2 deletions

File tree

modules/release-notes/pages/relnotes.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,9 @@
22
:page-aliases: analytics:releasenote
33
:description: Couchbase Server 7.6.x introduces multiple new features and fixes, as well as some deprecations and removals.
44
:page-toclevels: 2
5+
:stem:
6+
7+
include::partial$docs-server-7.6.8-release-note.adoc[]
58

69
include::partial$docs-server-7.6.7-release-note.adoc[]
710

Lines changed: 149 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,149 @@
1+
2+
[#release-768]
3+
== Release 7.6.8 (November 2025)
4+
5+
Couchbase Server 7.6.8 was released in November 2025.
6+
This maintenance release contains fixes to issues.
7+
8+
== Fixed Issues
9+
10+
11+
12+
13+
=== Cluster Manager
14+
[#table-fixed-issues-768-cluster-manager, cols='10,40,40']
15+
|===
16+
|Issue | Description | Resolution
17+
18+
19+
|https://jira.issues.couchbase.com/browse/MB-67106/[MB-67106]
20+
21+
a|*Metric Rename – Cache Miss Ratio → Get Miss Ratio*
22+
The _Cache Miss Ratio_ metric name suggested it measured memory or disk caching performance.
23+
In practical instances, as of version 7.6.2, it was redefined to measure the proportion of read (`get`) operations that fail because the requested key is not present in the bucket at all.
24+
To eliminate this confusion, the metric has been renamed to *Get Miss Ratio*.
25+
26+
| Issue resolved
27+
28+
29+
|https://jira.issues.couchbase.com/browse/MB-67758/[MB-67758]
30+
31+
a|Prior to the 7.6.8 release, the auto-failover pop up alerts, as documented in link:https://docs.couchbase.com/server/current/manage/manage-settings/configure-alerts.html#saving-and-testing-the-alert-configuration[Saving and Testing the Alert Configuration] did not work.
32+
33+
This has been fixed.
34+
35+
| Issue resolved
36+
37+
38+
|===
39+
40+
41+
42+
=== Data Service
43+
[#table-fixed-issues-768-data-service, cols='10,40,40']
44+
|===
45+
|Issue | Description | Resolution
46+
47+
48+
|https://jira.issues.couchbase.com/browse/MB-66876/[MB-66876]
49+
50+
a|The `magma_min_value_block_size_threshold` has been adjusted to INT_MAX for version 7.6.x, ensuring that block compression applies consistently for documents larger than 64 KiB.
51+
This change is not required for version 8.0.0 due to differences in configuration management.
52+
Couchbase recommends that if `magma_per_document_compression_enabled` is set to false, `magma_min_value_block_size_threshold` should also be set to `infinity` to maintain compression behavior.
53+
This resolves an issue with the Magma storage engine not compressing documents during persistence, which has been addressed in recent builds.
54+
The changes are confirmed and the ticket is closed after reviewing the code updates.
55+
56+
// Generated by [chatgpt:gpt-4o]
57+
58+
| Issue resolved
59+
60+
61+
|https://jira.issues.couchbase.com/browse/MB-67106/[MB-67106]
62+
63+
a|*Metric Rename – Cache Miss Ratio → Get Miss Ratio*
64+
The _Cache Miss Ratio_ metric name suggested it measured memory or disk caching performance.
65+
In reality, as of version 7.6.2, it was redefined to measure the proportion of read (`get`) operations that fail because the requested key is not present in the bucket at all.
66+
To eliminate this confusion, the metric has been renamed to *Get Miss Ratio*.
67+
68+
| Issue resolved
69+
70+
71+
|===
72+
73+
74+
75+
76+
77+
=== XDCR
78+
[#table-fixed-issues-768-xdcr, cols='10,40,40']
79+
|===
80+
|Issue | Description | Resolution
81+
82+
83+
|https://jira.issues.couchbase.com/browse/MB-66649/[MB-66649]
84+
85+
a|When modifying filter expressions or mapping configurations (explicit/migration), race conditions may prevent proper replication from the source.
86+
This can result in source bucket documents failing to replicate to the target bucket.
87+
To address this issue, the system now displays an alert when detecting replication resuming from stale checkpoints.
88+
This alert notifies users to delete and recreate the affected replication.
89+
IMPORTANT: Do not dismiss this alert by pausing and resuming the replication, as this will hide the warning without resolving the underlying issue.
90+
91+
| Issue resolved
92+
93+
94+
|===
95+
96+
97+
98+
=== Query Service
99+
[#table-fixed-issues-768-query-service, cols='10,40,40']
100+
|===
101+
|Issue | Description | Resolution
102+
103+
104+
|https://jira.issues.couchbase.com/browse/MB-66703/[MB-66703]
105+
106+
a|Added a plan version to prepared statements and logic to trigger reprepare when outdated plans are detected.
107+
This avoids duplicate OFFSET execution in mixedmode clusters due to changes in ORDER BY and LIMIT/OFFSET handling.
108+
109+
| Issue resolved
110+
111+
112+
|https://jira.issues.couchbase.com/browse/MB-67849/[MB-67849]
113+
114+
a|The recent builds of Couchbase Server versions 7.2.7 through 8.1.0 and Enterprise Analytics 2.1.0 include updates from the `go_json` library to address int64 overflow issues reported under MB-67849.
115+
The updates involve implementing proper checks for int64 overflow to properly represent large numbers (greater than 2^63^or less than -2^63^).
116+
117+
| Issue resolved
118+
119+
120+
|===
121+
122+
123+
124+
125+
126+
127+
128+
129+
130+
131+
132+
=== Tools
133+
[#table-fixed-issues-768-tools, cols='10,40,40']
134+
|===
135+
|Issue | Description | Resolution
136+
137+
138+
|https://jira.issues.couchbase.com/browse/MB-60676/[MB-60676]
139+
140+
a|Previously in clusters with the backup service running on multiple nodes it was possible for more than one task on a repo to be attempted at the same, causing all but one of these tasks to fail.
141+
If multiple tasks are scheduled to run at the same time, we now skip all but the first one.
142+
143+
| Issue resolved
144+
145+
146+
|===
147+
148+
149+

preview/HEAD.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
sources:
2-
docs-server:
3-
branches: [DOC-13396-Create-release-note-for-7.6.7-Release,DOC-13372-Create-release-note-for-docs-server-7.2.8]
42
docs-devex:
53
branches: release/7.6
64
cb-swagger:

0 commit comments

Comments
 (0)