|
| 1 | + |
| 2 | + |
| 3 | + |
| 4 | + |
| 5 | + |
| 6 | +[#breaking-changes-80] |
| 7 | +== Breaking changes 8.0 (August 2025) |
| 8 | + |
| 9 | +Couchbase Server 8.0 was released in August 2025. |
| 10 | +This maintenance release contains the following breaking changes: |
| 11 | + |
| 12 | + |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | + |
| 19 | +=== Data Service |
| 20 | + |
| 21 | +[#breaking-changes-80-data-service] |
| 22 | + |
| 23 | + |
| 24 | +*https://jira.issues.couchbase.com/browse/MB-63946/[MB-63946]*:: |
| 25 | + |
| 26 | +When using `mcstat` it is no longer possible to use `--json=pretty`. |
| 27 | +The request to pretty-print the JSON is ignored |
| 28 | ++ |
| 29 | +Users can use a pipe in conjunction with an external formatting tool such as `jq` to obtain formatted output: |
| 30 | ++ |
| 31 | +[source, shell] |
| 32 | + |
| 33 | +---- |
| 34 | +
|
| 35 | +./mcstat [options] --json [statgroup] \| jq . |
| 36 | +
|
| 37 | +---- |
| 38 | + |
| 39 | +*https://jira.issues.couchbase.com/browse/MB-63938/[MB-63938]*:: |
| 40 | + |
| 41 | +The latest builds, couchbase-server-8.0.0-1964 and couchbase-columnar-1.2.0-1009, include a critical update from the kv_engine commit 0e2fa3c. This update addresses issue MB-63938, ensuring that mcstat now only accepts a single stat group at a time. This change improves consistency and accuracy in data handling by preventing multiple stat groups from being processed simultaneously. The update is included in both new builds to ensure unified functionality across platforms. |
| 42 | + |
| 43 | +// Generated by [chatgpt:gpt-4o] |
| 44 | + |
| 45 | + |
| 46 | +*https://jira.issues.couchbase.com/browse/MB-9418/[MB-9418]*:: |
| 47 | + |
| 48 | +The latest update introduces "Secondary Warmup" in Couchbase Server 8.0.0, allowing the warmup process to page in items even after reaching minimum thresholds. This enhancement helps improve availability by letting the bucket become write-accessible more quickly during warmup. Users can now choose between three warmup behaviors: "blocking" (traditional warmup), "background" (secondary warmup), and "none" (disabling warmup). These settings can be configured via a new parameter, `warmup_behavior`, simplifying user configuration. Tests confirmed that running primary and secondary warmups simultaneously can lead to resource inefficiencies, thus users are advised to choose either all-primary or all-secondary configurations. Upgrades will default to the secondary warmup scheme, with the option to revert to legacy behavior if required. This change increases flexibility and potential performance during the warmup phase. |
| 49 | + |
| 50 | +// Generated by [chatgpt:gpt-4o] |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +=== Views |
| 55 | + |
| 56 | +[#breaking-changes-80-views] |
| 57 | + |
| 58 | + |
| 59 | +*https://jira.issues.couchbase.com/browse/MB-67280/[MB-67280]*:: |
| 60 | + |
| 61 | +The Bucket Priority option, previously used to prioritize tasks for certain buckets, has been removed from the UI due to changes in the task scheduler backend since version 7.0. The transition to the FollyExecutorPool, which does not utilize bucket priority, rendered the setting ineffective. Despite its removal from the UI, the option remains available in the REST API to maintain backward compatibility. Previously, bucket priorities allowed tasks to be grouped into high or low priority queues, but the newer implementation and increased thread pool sizes have mitigated the need for such prioritization. These changes are reflected in recent builds across various Couchbase server versions. |
| 62 | + |
| 63 | +// Generated by [chatgpt:gpt-4o] |
| 64 | + |
| 65 | + |
| 66 | +*https://jira.issues.couchbase.com/browse/MB-63212/[MB-63212]*:: |
| 67 | + |
| 68 | +The UI will no longer display the option to add memcached buckets as part of ongoing improvements. When users attempt to create a memcached bucket, clicking "Add Bucket" currently yields no response, and an update is planned to return an error message instead. Changes were merged into the Morpheus project and validated on version 8.0.0-2016. The issue arises even with older UI versions when connected to mixed version clusters. The UI's behavior regarding error handling for bucket creation is under review, as current feedback suggests it doesn't currently manage all error messages effectively. These updates are part of commit 6900275. |
| 69 | + |
| 70 | +// Generated by [chatgpt:gpt-4o] |
| 71 | + |
| 72 | + |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | + |
| 77 | + |
| 78 | + |
| 79 | + |
| 80 | + |
| 81 | + |
| 82 | +=== Index Service |
| 83 | + |
| 84 | +[#breaking-changes-80-index-service] |
| 85 | + |
| 86 | + |
| 87 | +*https://jira.issues.couchbase.com/browse/MB-63192/[MB-63192]*:: |
| 88 | + |
| 89 | +The latest update, couchbase-columnar-1.2.0-1009, introduces a series of enhancements and tests primarily focused on the shard dealer functionality. This includes moving to the maxDiskUsagePerShard config, leveraging shard stats from Indexer, and ensuring index-replica positioning. The update addresses both index and slot-replica management, refactoring of shard dealer code, and adding various tests across multiple passes, ensuring robust handling of shard dealer operations. The new version implements a more aggressive shard sharing strategy, which may affect performance in 8.0 compared to 7.6 but allows for more dynamic resource allocation. A feature flag controls the new distribution algorithm, offering flexibility to revert to the previous behavior if needed. The update also details expected behavior during upgrades and provides considerations for both on-prem and online clusters. Performance impacts are expected to be minor, but further validation through testing will be conducted to confirm this. |
| 90 | + |
| 91 | +// Generated by [chatgpt:gpt-4o] |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | + |
| 96 | + |
| 97 | +=== Tools |
| 98 | + |
| 99 | +[#breaking-changes-80-tools] |
| 100 | + |
| 101 | + |
| 102 | +*https://jira.issues.couchbase.com/browse/MB-63389/[MB-63389]*:: |
| 103 | + |
| 104 | +The CLI has been updated to remove memcached buckets in Couchbase version 8.0 and above, aligning with the latest standards. This change is reflected starting from builds 8.0.0-2117 and 8.0.0-2302, where creating memcached buckets will result in an error, advising the use of ephemeral buckets instead. The transition aims to maintain administration compatibility with older clusters, thus version checks have been reinforced. The bucket creation command still shows 'memcached' as an option, but it is no longer functional. These updates ensure that CLI admin tools are consistent across newer server installations, reinforcing stability and future-proofing. |
| 105 | + |
| 106 | +// Generated by [chatgpt:gpt-4o] |
| 107 | + |
| 108 | + |
| 109 | +*https://jira.issues.couchbase.com/browse/MB-60337/[MB-60337]*:: |
| 110 | + |
| 111 | +The latest update introduces a change where deleting backups that cause incremental backups to become invalid is now restricted by default. Users attempting to delete such backups will encounter an error unless they use the new `--disable-safe-remove-check` flag to override this restriction. This change aims to prevent potential issues with incremental backups. The feature has been validated and is available in the specified builds, though a minor bug has been identified and will be tracked separately. Users relying on previous deletion behavior can still access it through the mentioned flag. |
| 112 | + |
| 113 | +// Generated by [chatgpt:gpt-4o] |
| 114 | + |
| 115 | + |
| 116 | + |
| 117 | + |
0 commit comments