|
| 1 | + |
| 2 | + |
| 3 | +[#release-768] |
| 4 | +== Release 7.6.8 (October 2025) |
| 5 | + |
| 6 | +Couchbase Server 7.6.8 was released in October 2025. |
| 7 | +This maintenance release contains fixes to issues. |
| 8 | + |
| 9 | +== Fixed Issues |
| 10 | + |
| 11 | + |
| 12 | + |
| 13 | + |
| 14 | +=== Cluster Manager |
| 15 | + |
| 16 | +[#table-known-issues-768-cluster-manager, cols="10,40,40"] |
| 17 | +|=== |
| 18 | +|Issue | Description | Resolution |
| 19 | + |
| 20 | +| https://jira.issues.couchbase.com/browse/MB-67106/[MB-67106] |
| 21 | + |
| 22 | +a| The "Cache Miss Ratio" metric has been revised for clarification. It no longer refers to memory/disk caching but to read operations failing due to keys not being present in the bucket. We've renamed this to "Get Miss Ratio" to avoid confusion. The previous metrics, ep_cache_miss_rate and kv_ep_cache_miss_ratio, will be deprecated but retained temporarily. The UI will remove the term "cache," and a future update may introduce a "Disk Lookups" metric to track disk access operations. Deprecated stats will be phased out once a process for removal is established, with the eventual introduction of more relevant metrics directly through the KV-Engine. |
| 23 | + |
| 24 | +// Generated by [chatgpt:gpt-4o] |
| 25 | + |
| 26 | +| Issue resolved |
| 27 | + |
| 28 | +| https://jira.issues.couchbase.com/browse/MB-67758/[MB-67758] |
| 29 | + |
| 30 | +a| Auto-failover alerts now support UI pop-ups, improved in multiple builds, including couchbase-server-7.6.8-7006, 8.0.0-3554, 8.1.0-1021, enterprise-analytics-2.0.1-1205, and 2.1.0-1013. While testing, a five-node cluster showed pop-up alerts when nodes failed, confirming the feature's effectiveness. Disabling alerts as expected resulted in no pop-ups. These enhancements aim to improve user interaction and monitoring by displaying alerts directly on the UI during auto-failover scenarios, helping users respond swiftly to node failures. |
| 31 | + |
| 32 | +// Generated by [chatgpt:gpt-4o] |
| 33 | + |
| 34 | +| Issue resolved |
| 35 | + |
| 36 | +|=== |
| 37 | + |
| 38 | + |
| 39 | +=== Data Service |
| 40 | + |
| 41 | +[#table-known-issues-768-data-service, cols="10,40,40"] |
| 42 | +|=== |
| 43 | +|Issue | Description | Resolution |
| 44 | + |
| 45 | +| https://jira.issues.couchbase.com/browse/MB-66876/[MB-66876] |
| 46 | + |
| 47 | +a| The `magma_min_value_block_size_threshold` has been adjusted from 64KB to INT_MAX for version 7.6.x to resolve an issue where buckets using the Magma storage engine did not apply block compression for documents larger than 64 KiB. This fix is included in build couchbase-server-7.6.7-6464. There's no change needed for version 8.0.0, as kv_engine overrides the config. It's noted that if `magma_per_document_compression_enabled` is set to false, `magma_min_value_block_size_threshold` should be set to infinity. This adjustment ensures that block compression applies as intended during persistence. |
| 48 | + |
| 49 | +// Generated by [chatgpt:gpt-4o] |
| 50 | + |
| 51 | +| Issue resolved |
| 52 | + |
| 53 | +| https://jira.issues.couchbase.com/browse/MB-67106/[MB-67106] |
| 54 | + |
| 55 | +a| The "Cache Miss Ratio" metric has been revised for clarification. It no longer refers to memory/disk caching but to read operations failing due to keys not being present in the bucket. We've renamed this to "Get Miss Ratio" to avoid confusion. The previous metrics, ep_cache_miss_rate and kv_ep_cache_miss_ratio, will be deprecated but retained temporarily. The UI will remove the term "cache," and a future update may introduce a "Disk Lookups" metric to track disk access operations. Deprecated stats will be phased out once a process for removal is established, with the eventual introduction of more relevant metrics directly through the KV-Engine. |
| 56 | + |
| 57 | +// Generated by [chatgpt:gpt-4o] |
| 58 | + |
| 59 | +| Issue resolved |
| 60 | + |
| 61 | +|=== |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | + |
| 66 | +=== XDCR |
| 67 | + |
| 68 | +[#table-known-issues-768-xdcr, cols="10,40,40"] |
| 69 | +|=== |
| 70 | +|Issue | Description | Resolution |
| 71 | + |
| 72 | +| https://jira.issues.couchbase.com/browse/MB-66649/[MB-66649] |
| 73 | + |
| 74 | +a| The latest builds of Couchbase Server, 7.6.7-6414 and 7.6.7-6422, include updates from the goxdcr project focused on UX enhancements for the Trinity UI. These improvements serve as an alternative to backporting changes from MB-66140. The 6414 build incorporates the commit for these UX enhancements, while the 6422 build includes a fix for the TestPipelineOpSerializerReinit unit test. These updates aim to streamline user experience and ensure reliable functionality within the platform. |
| 75 | + |
| 76 | +// Generated by [chatgpt:gpt-4o] |
| 77 | + |
| 78 | +| Issue resolved |
| 79 | + |
| 80 | +|=== |
| 81 | + |
| 82 | + |
| 83 | +=== Query Service |
| 84 | + |
| 85 | +[#table-known-issues-768-query-service, cols="10,40,40"] |
| 86 | +|=== |
| 87 | +|Issue | Description | Resolution |
| 88 | + |
| 89 | +| https://jira.issues.couchbase.com/browse/MB-67849/[MB-67849] |
| 90 | + |
| 91 | +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 and adding corresponding unit tests. These modifications have been verified across multiple versions, ensuring accurate representation of large integers. Improvements have been applied consistently to maintain system integrity and performance. The changes also include two major commits focusing on overflow checks and additional unit testing to ensure robustness and reliability. The updates aim to prevent erroneous handling of large integer values within the database operations. |
| 92 | + |
| 93 | +// Generated by [chatgpt:gpt-4o] |
| 94 | + |
| 95 | +| Issue resolved |
| 96 | + |
| 97 | +|=== |
| 98 | + |
| 99 | + |
| 100 | + |
| 101 | + |
| 102 | + |
| 103 | + |
| 104 | + |
| 105 | + |
| 106 | + |
| 107 | + |
| 108 | +=== Tools |
| 109 | + |
| 110 | +[#table-known-issues-768-tools, cols="10,40,40"] |
| 111 | +|=== |
| 112 | +|Issue | Description | Resolution |
| 113 | + |
| 114 | +| https://jira.issues.couchbase.com/browse/MB-60676/[MB-60676] |
| 115 | + |
| 116 | +a| In the latest release, an update has been implemented to prevent multiple scheduled jobs for the same repository from running concurrently across backup service nodes in a cluster. This resolves an issue where concurrent jobs resulted in failures. The update, aligning with commit MB-60676, ensures only one task per repository is executed at any time. The change has been validated on build 8.0.0-2920. Additionally, there is an update to the cbauth module as part of this release. These improvements aim to enhance job scheduling stability within the system. |
| 117 | + |
| 118 | +// Generated by [chatgpt:gpt-4o] |
| 119 | + |
| 120 | +| Issue resolved |
| 121 | + |
| 122 | +|=== |
| 123 | + |
| 124 | + |
0 commit comments