Skip to content

Commit fe3ee75

Browse files
committed
[DOC-13372]: Create release note for Couchbase Server 7.2.8
Signed-off-by: Ray Offiah <[email protected]>
1 parent 7694352 commit fe3ee75

File tree

2 files changed

+133
-0
lines changed

2 files changed

+133
-0
lines changed

modules/release-notes/pages/relnotes.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
11
= Release Notes for Couchbase Server 7.2
2+
:stem:
3+
4+
include::partial$docs-server-7.2.8-release-note.adoc[]
25

36
include::partial$docs-server-7.2.7-release-note.adoc[]
47

Lines changed: 130 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,130 @@
1+
2+
3+
[#release-728]
4+
== Release 7.2.8 (August 2025)
5+
6+
Couchbase Server 7.2.8 was released in August 2025.
7+
This maintenance release contains fixes to issues.
8+
9+
== Fixed Issues
10+
11+
12+
13+
14+
15+
16+
=== Data Service
17+
18+
[#table-known-issues-728-data-service, cols="10,40,40"]
19+
|===
20+
|Issue | Description | Resolution
21+
22+
23+
| https://jira.issues.couchbase.com/browse/MB-67762[MB-67762]
24+
a|There is an integer overflow bug in buckets using the Magma storage engine.
25+
This bug can potentially cause a subset of mutations to become invisible to read operations after approximately 500 billion to 2 trillion mutations per bucket.  
26+
| For details, please refer to https://jira.issues.couchbase.com/browse/MB-67762[MB-67762]
27+
28+
29+
|===
30+
31+
32+
33+
34+
=== XDCR
35+
36+
[#table-known-issues-728-xdcr, cols="10,40,40"]
37+
|===
38+
|Issue | Description | Resolution
39+
40+
41+
| https://jira.issues.couchbase.com/browse/MB-66650/[MB-66650]
42+
43+
a| When modifying filter expressions or mapping configurations (explicit/migration), race conditions may prevent proper replication from the source. This can result in source bucket documents failing to replicate to the target bucket.
44+
To address this issue, the system now displays an alert when detecting replication resuming from stale checkpoints. This alert notifies users to delete and recreate the affected replication.
45+
IMPORTANT: Do not dismiss this alert by pausing and resuming the replication, as this will hide the warning without resolving the underlying issue.
46+
47+
| Issue resolved
48+
49+
50+
|===
51+
52+
53+
=== Query Service
54+
55+
[#table-known-issues-728-query-service, cols="10,40,40"]
56+
|===
57+
|Issue | Description | Resolution
58+
59+
60+
| https://jira.issues.couchbase.com/browse/MB-67849/[MB-67849]
61+
62+
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. The updates involve implementing proper checks for int64 overflow in order to properly represent large numbers (greater than stem:[2^63] or less than stem:[-2^63]).
63+
64+
| Issue resolved
65+
66+
67+
|===
68+
69+
70+
71+
72+
73+
74+
=== Index Service
75+
76+
[#table-known-issues-728-index-service, cols="10,40,40"]
77+
|===
78+
|Issue | Description | Resolution
79+
80+
81+
| https://jira.issues.couchbase.com/browse/MB-66034/[MB-66034]
82+
83+
a| Previously, during smart batching, the calculation of `max concurrent builds per node` incorrectly considered all indexer nodes as potential destinations; even those not participating in index movement during the rebalance. As a result, the destination node count was inflated, causing the batch size to be divided across more nodes than necessary. This led to smaller batch sizes and fewer tokens per batch on the actual recipient nodes.
84+
With this fix, only indexer nodes that are actively receiving index transfers are considered in the destination node count. This results in more accurate batch sizing and improved efficiency during index rebalance operations.
85+
86+
| Issue resolved
87+
88+
89+
90+
| https://jira.issues.couchbase.com/browse/MB-67116/[MB-67116]
91+
92+
a| A race condition in the projector service could cause a deadlock when closing streams with high mutation rates. The issue, present since version 7.2.2, didn't affect functionality but resulted in increased memory consumption as mutations in the pipeline couldn't be released properly.
93+
With this fix, memory usage has been restored to normal levels.
94+
95+
| Issue resolved
96+
97+
98+
99+
| https://jira.issues.couchbase.com/browse/MB-67118/[MB-67118]
100+
101+
a| `DropInstanceToken` increased in size due to changes in the definition. With more partitions, its size can increase beyond the `metakv` size limit.
102+
This ticket fixes the issue by using `BigValueGet` with `DropInstanceToken` which splits the tokens in parts, stores them in `metakv`, and retrieves the token by combining the parts.
103+
Before this patch, replica drops were failing when the token increased in size as retrieval was failing.
104+
105+
| Issue resolved
106+
107+
108+
|===
109+
110+
111+
112+
113+
=== Tools
114+
115+
[#table-known-issues-728-tools, cols="10,40,40"]
116+
|===
117+
|Issue | Description | Resolution
118+
119+
120+
| https://jira.issues.couchbase.com/browse/MB-57755/[MB-57755]
121+
122+
a| Beginning with Server 7.2.8/7.6.7, when installing on a Linux system using cgroups v1, Server will set the `memory.swappiness` cgroups parameter to `0` for the `couchbase-server` service slice. This ensures best performance without affecting any other services that may be running on the system.
123+
For Linux systems using cgroups v2 (which is the default for the more recent releases of most Linux distributions), there is no `memory.swappiness` parameter for individual service slices. Therefore it is still highly recommended to set kernel swappiness to `0` globally on each node, as explained in the documentation: https://docs.couchbase.com/server/current/install/install-swap-space.html
124+
125+
| Issue resolved
126+
127+
128+
|===
129+
130+

0 commit comments

Comments
 (0)