You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cache Miss Ratio metric has been redefined to more accurately represent its function, as it previously suggested involvement with memory/disk caching. This term has now changed to "Get Miss Ratio" to clarify it refers to read operations where the key is absent. The renaming aligns with metric calculations that report keys not existing. The "ep_cache_miss" metrics are deprecated but will remain temporarily to support existing graphs until they can be fully removed. Future releases may introduce metrics like "kv_ep_bgfetched" to track disk lookups, addressing the misperceived role of the Cache Miss Ratio. The update was influenced by community feedback and aims to direct users toward documented Data Service metrics for clarity.
24
+
The Cache Miss Ratio metric has been renamed to "Miss Ratio" to clarify its definition, which refers to keys not present in the bucket rather than memory/disk caching. The terms "ep_cache_miss_rate" and "kv_ep_cache_miss_ratio" are deprecated and maintained for legacy support. Future considerations include possibly introducing the "kv_ep_bgfetched" metric as "Disk Lookups" in UI dashboards to indicate operations requiring disk access. The deprecated metrics will be removed once a standard process for deprecation is established. Users are encouraged to rely on documented metrics for more accurate insights. The changes are reflected in build couchbase-server-8.0.0-3317.
25
25
26
26
// Generated by [chatgpt:gpt-4o]
27
27
@@ -34,25 +34,25 @@ The Cache Miss Ratio metric has been redefined to more accurately represent its
The latest build of Couchbase Server 8.0.0-1545 and Couchbase Columnar 1.2.0-1009 now includes updates from the kv_engine commit fd8914a. This commit introduces parsing and dumping capabilities for "deprecated" and "notes" fields in the `gen_stat_definitions.cc` file. The update is part of effort MB-60542 and is applied consistently across the builds. This enhancement aims to improve metadata handling by addressing the need to manage legacy and additional information more effectively. Links to the specific changes and issue details are provided for further reference.
37
+
The latest updates include changes from kv_engine commit fd8914a, which addresses MB-60542. This update introduces the parsing and dumping of "deprecated" and "notes" fields in `gen_stat_definitions.cc`. These enhancements are implemented in builds couchbase-server-8.0.0-1545 and couchbase-columnar-1.2.0-1009. The modifications ensure improved data handling and compliance with new field requirements. Users can refer to the commit details and associated issue MB-60542 for more information.
SET and DELETE with Meta operations could distort the vbucket max_cas if a faulty CAS value is provided in the operation, setting the vbuckets max_cas to an unusually high or inconsistent value. Inadvertently affecting the Hybrid Logical Clock (HLC) and Last Write Wins (LLW) conflict resolution via XDCR. In certain cases, this resulted in legitimate mutations being skipped or ignored during replication. For this reason, the system now fails front-end operations with a CAS value that exceeds the {{hlc_max_future_threshold}}, default value of 65 minutes, to prevent a vbucket’s max_cas from getting distorted.
44
+
SET and DELETE with Meta operations could distort the vbucket max_cas if a faulty CAS value is provided in the operation, setting the vbuckets max_cas to an unusually high or inconsistent value. Inadvertently affecting the Hybrid Logical Clock (HLC) and Last Write Wins (LLW) conflict resolution via XDCR. In certain cases, this resulted in legitimate mutations being skipped or ignored during replication. For this reason, the system now fails front-end operations with a CAS value that exceeds the `hlc_max_future_threshold`, default value of 65 minutes, to prevent a vbucket’s max_cas from getting distorted.
Couchbase Server version 8.0.0-2772 includes an indexing update with commit c8f3dab, addressing issue MB-65644. The plasma configuration option enableCompressFullMarshal is now set to false to improve performance. This change will be finalized in version 8.0.0-2905. Refer to the [GitHub commit](https://github.com/couchbase/indexing/commit/c8f3dab54a4f5fe4f93f98b657ccc03f93d28dd8) for further details.
48
+
In Couchbase Server 8.0.0-2772, the indexing component includes a change from commit [c8f3dab](https://github.com/couchbase/indexing/commit/c8f3dab54a4f5fe4f93f98b657ccc03f93d28dd8) addressing issue [MB-65644](https://jira.issues.couchbase.com/browse/MB-65644). The update involves setting the plasma configuration option `enableCompressFullMarshal` to false. This adjustment will be finalized in version 8.0.0-2905.
The Cache Miss Ratio metric has been redefined to more accurately represent its function, as it previously suggested involvement with memory/disk caching. This term has now changed to "Get Miss Ratio" to clarify it refers to read operations where the key is absent. The renaming aligns with metric calculations that report keys not existing. The "ep_cache_miss" metrics are deprecated but will remain temporarily to support existing graphs until they can be fully removed. Future releases may introduce metrics like "kv_ep_bgfetched" to track disk lookups, addressing the misperceived role of the Cache Miss Ratio. The update was influenced by community feedback and aims to direct users toward documented Data Service metrics for clarity.
55
+
The Cache Miss Ratio metric has been renamed to "Miss Ratio" to clarify its definition, which refers to keys not present in the bucket rather than memory/disk caching. The terms "ep_cache_miss_rate" and "kv_ep_cache_miss_ratio" are deprecated and maintained for legacy support. Future considerations include possibly introducing the "kv_ep_bgfetched" metric as "Disk Lookups" in UI dashboards to indicate operations requiring disk access. The deprecated metrics will be removed once a standard process for deprecation is established. Users are encouraged to rely on documented metrics for more accurate insights. The changes are reflected in build couchbase-server-8.0.0-3317.
56
56
57
57
// Generated by [chatgpt:gpt-4o]
58
58
@@ -65,7 +65,7 @@ The Cache Miss Ratio metric has been redefined to more accurately represent its
The latest build, couchbase-server-8.0.0-1668, includes a significant update with the introduction of a symbolic link for the audit log, specifically addressed in kv_engine commit db74893. This update resolves issue MB-62295, ensuring streamlined audit log management. The change has been validated on build 8.0.0-2236 and effectively closes the ticket. Users are not expected to notice any disruption or change in performance with this update.
68
+
The latest build of Couchbase Server 8.0.0-1668 incorporates a key update in the kv_engine, specifically commit db74893, which introduces symbolic links for audit logs to facilitate easier file management. This enhancement was validated successfully on build 8.0.0-2236 and resulted in the closing of ticket MB-62295. Users should not notice any disruption as a result of this change, as it primarily affects backend file handling. Additionally, the Couchbase Columnar 1.2.0-1009 build includes the same commit, further extending this improvement across platforms. This update ensures streamlined audit log processing and reduces manual handling effort.
69
69
70
70
// Generated by [chatgpt:gpt-4o]
71
71
@@ -78,7 +78,7 @@ The latest build, couchbase-server-8.0.0-1668, includes a significant update wit
In the latest update, the "Cache Miss Ratio" metric has been renamed to "Get Miss Ratio" to clarify its purpose. This change aims to avoid confusion since the metric does not measure cache misses, but rather the percentage of read operations where the key is not found. The decision was made to maintain consistency with existing "Get" metrics. Although the internal metric name, `kv_ep_cache_miss_ratio`, remains unchanged to prevent disruption to customer scripts, the UI now provides a pop-up description to clarify the metric's meaning. This update is included in build couchbase-server-8.0.0-3417.
81
+
The "Cache Miss Ratio" metric has been renamed to "Get Miss Ratio" to clarify its purpose. Initially misleading, the metric actually measures the fraction of read operations that fail due to the key not being present in the bucket. This change was agreed upon to avoid confusion with cache-related metrics. Although there was a suggestion to rename it to "Key Not Found Ratio," it was decided that "Get Miss Ratio" would be more consistent with existing terminology. This update appears in the UI, even though the underlying stat name remains unchanged for compatibility reasons. The change is part of build couchbase-server-8.0.0-3417, as documented in the commit 80a0668.
82
82
83
83
// Generated by [chatgpt:gpt-4o]
84
84
@@ -139,7 +139,7 @@ INSERT and UPSERT statement OPTIONS may now include an “xattrs” object eleme
Eventing integration with App Services has been updated to handle syncing challenges with the "_sync" system xattr on Couchbase Capella. This issue occurred due to differences in how Sync Gateway registry objects are structured in cloud deployments, leading to parsing failures. The root cause involved an extra "config" object that wasn't present in on-prem deployments. Patches have been created and are under review for inclusion in upcoming releases, specifically targeting versions 7.6.4 and later. Testing has verified that eventing functions now deploy correctly with source keyspace bindings, ensuring smooth document mutations as intended. The fix has been tested against Couchbase Server 8.0.0-3095, demonstrating compatibility and functionality.
142
+
Eventing with App Services experienced an issue related to the Sync Gateway registry parser. The root cause was identified as a mismatch in the registry structure between cloud and on-prem deployments. This led to failures in parsing due to differences in the xattr configuration key. Patches have been developed and are under review, targeting a fix in the upcoming 7.6.4 release. Testing confirmed the integration works as expected with CBS version 8.0.0-3095. Future deployments will ensure compatibility through Capella-specific smoke tests. The fixes are scheduled for merging by November 5th.
143
143
144
144
// Generated by [chatgpt:gpt-4o]
145
145
@@ -157,6 +157,17 @@ Eventing integration with App Services has been updated to handle syncing challe
157
157
When shard affinity is enabled, the indexer internally maps all replicas of an index to an alternateID. If such an alternateID exists on a node outside the list of nodes, instead of preventing replica creation, the system creates a new replica with the same alternateID on different nodes. This leads to rebalance failures on the affected nodes.
The latest update introduces a feature to include the return distance of a hit in the DocumentMatch response for geo distance queries. This improvement allows for the distance to be displayed in a user-readable format if a geo sort is applied, enhancing the search JSON response without altering existing functionality. The response structure remains backward compatible, displaying the distance only when calculated. This addition is thoroughly tested to ensure reliability. This update marks a crucial enhancement by decoding previously encoded distance values, making them accessible for better user interaction. The feature is now pending final approvals before being integrated into Morpheus.
0 commit comments