From 389a41f15e755b2627a225364714671a5292c439 Mon Sep 17 00:00:00 2001 From: supritha-kumar Date: Mon, 12 Jan 2026 10:25:06 +0530 Subject: [PATCH 1/5] DOC-13853 Change in behaviour for Log File rotation in 8.0 https://jira.issues.couchbase.com/browse/DOC-13853 --- modules/manage/pages/manage-logging/manage-logging.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/modules/manage/pages/manage-logging/manage-logging.adoc b/modules/manage/pages/manage-logging/manage-logging.adoc index c8113c31bf..69edc6a3f0 100644 --- a/modules/manage/pages/manage-logging/manage-logging.adoc +++ b/modules/manage/pages/manage-logging/manage-logging.adoc @@ -240,9 +240,6 @@ Couchbase Server rotates log files to prevent them from consuming too much disk It keeps a limited number of past log files in compressed format for reference. Once it reaches the limit on the number of logs files to keep, Couchbase Server deletes the oldest log file. -By default, Couchbase Server rotates the `memcached` log file when it reaches 10{nbsp}MB in size. -In addition to the current uncompressed log file, it keeps 19 past logs. - Couchbase Server rotates other log files automatically when they reach 40{nbsp}MB. It keeps the current version of the log, plus up to 9 compressed past logs. From abffd563294edd5ced652b9aa936d6e840ebd6af Mon Sep 17 00:00:00 2001 From: Supritha Date: Tue, 27 Jan 2026 13:12:21 +0530 Subject: [PATCH 2/5] Updated for bug DOC-13853 --- .../pages/manage-logging/manage-logging.adoc | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/modules/manage/pages/manage-logging/manage-logging.adoc b/modules/manage/pages/manage-logging/manage-logging.adoc index 69edc6a3f0..808158c7b4 100644 --- a/modules/manage/pages/manage-logging/manage-logging.adoc +++ b/modules/manage/pages/manage-logging/manage-logging.adoc @@ -240,7 +240,20 @@ Couchbase Server rotates log files to prevent them from consuming too much disk It keeps a limited number of past log files in compressed format for reference. Once it reaches the limit on the number of logs files to keep, Couchbase Server deletes the oldest log file. -Couchbase Server rotates other log files automatically when they reach 40{nbsp}MB. +In Couchbase Server 8.0 and later, Memcached log retention is based on total disk usage (aggregated size) rather than a fixed number of rotated files. +By default, the Memcached log rotates when it reaches ~10 MB. + +Couchbase Server retains multiple rotated Memcached log files until the combined size of all retained files exceeds a configured aggregate limit. +When you exceed the aggregated size limit, Couchbase Server removes the oldest rotated files as part of the next rotation cycle. +The default aggregate retention cap is 500 MB. + +In addition to size-based rotation, Couchbase Server starts a new Memcached log file when: + +* You restart a node (you create a new log file on startup) +* You turn on or turn off encryption for Memcached logs +* You turn on encryption and a key rotation occurs + +Couchbase Server versions earlier than 8.0 rotates other log files automatically when they reach 40{nbsp}MB. It keeps the current version of the log, plus up to 9 compressed past logs. ==== Changing Log Rotation Settings @@ -251,7 +264,9 @@ It does not propagate to other nodes in the cluster. NOTE: Couchbase Server upgrades can overwrite `static_config`, losing any of your modifications. -To change log rotation settings, follow these steps: +In Couchbase 8.0+, Memcached log rotation uses internal configuration and an aggregate‑size retention limit, which you may not be able to configure in all releases. + +To change log rotation settings for non-Memcached logs, follow these steps: . Log into a node as `root` or the user who owns the Couchbase Server files. You can also use `sudo` to gain the necessary permissions. From 206620884163c6fb8f465da64daa14c6b3717e52 Mon Sep 17 00:00:00 2001 From: Supritha Date: Wed, 28 Jan 2026 09:56:03 +0530 Subject: [PATCH 3/5] incorporated review comments at https://github.com/couchbase/docs-server/pull/4066/changes#r2734794530 --- .../manage/pages/manage-logging/manage-logging.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/manage/pages/manage-logging/manage-logging.adoc b/modules/manage/pages/manage-logging/manage-logging.adoc index 808158c7b4..936c1907b2 100644 --- a/modules/manage/pages/manage-logging/manage-logging.adoc +++ b/modules/manage/pages/manage-logging/manage-logging.adoc @@ -245,15 +245,15 @@ By default, the Memcached log rotates when it reaches ~10 MB. Couchbase Server retains multiple rotated Memcached log files until the combined size of all retained files exceeds a configured aggregate limit. When you exceed the aggregated size limit, Couchbase Server removes the oldest rotated files as part of the next rotation cycle. -The default aggregate retention cap is 500 MB. +The default aggregate retention cap is 200 MB. In addition to size-based rotation, Couchbase Server starts a new Memcached log file when: -* You restart a node (you create a new log file on startup) -* You turn on or turn off encryption for Memcached logs -* You turn on encryption and a key rotation occurs +* You restart a Memcached process +* You enable or disable encryption for Memcached logs +* You enable encryption for Memcached logs and a key rotation occurs -Couchbase Server versions earlier than 8.0 rotates other log files automatically when they reach 40{nbsp}MB. +Couchbase Server versions earlier than 8.0 rotates non-Memcached log files automatically when they reach 40{nbsp}MB. It keeps the current version of the log, plus up to 9 compressed past logs. ==== Changing Log Rotation Settings From 739bfdf45c44ff1a57f7b1730b03009e7af38eb2 Mon Sep 17 00:00:00 2001 From: Supritha Date: Fri, 30 Jan 2026 09:24:27 +0530 Subject: [PATCH 4/5] incorporated comments from PR - https://github.com/couchbase/docs-server/pull/4073/changes --- .../learn/pages/buckets-memory-and-storage/storage-engines.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc index 30ede4fda1..21a82cfe7c 100644 --- a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc +++ b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc @@ -57,7 +57,7 @@ To learn more about configuring the Writer Thread settings for your Magma bucket Couchstore is the original storage engine for Couchbase Server. It's the only storage engine available in Couchbase Server Community Edition. Couchstore is designed for high performance with datasets that fit in memory. -It has a minimum memory requirement of 100{nbsp}MB per node, and a minimum memory-to-data ratio of 10%. +It has a minimum memory requirement of 100{nbsp}MB per node, and a recommended minimum memory-to-data ratio of 10%. If you have a small dataset whose working set (frequently accessed data) can fit in memory, then you should consider using Couchstore. == Couchstore verses Magma at a Glance From 2fdc0aa5bcc41ff4cd3f236f2131e2f8b175f062 Mon Sep 17 00:00:00 2001 From: Supritha Date: Mon, 2 Feb 2026 18:23:08 +0530 Subject: [PATCH 5/5] undid changes that I'd made by mistake - line 60 --- .../learn/pages/buckets-memory-and-storage/storage-engines.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc index 21a82cfe7c..30ede4fda1 100644 --- a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc +++ b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc @@ -57,7 +57,7 @@ To learn more about configuring the Writer Thread settings for your Magma bucket Couchstore is the original storage engine for Couchbase Server. It's the only storage engine available in Couchbase Server Community Edition. Couchstore is designed for high performance with datasets that fit in memory. -It has a minimum memory requirement of 100{nbsp}MB per node, and a recommended minimum memory-to-data ratio of 10%. +It has a minimum memory requirement of 100{nbsp}MB per node, and a minimum memory-to-data ratio of 10%. If you have a small dataset whose working set (frequently accessed data) can fit in memory, then you should consider using Couchstore. == Couchstore verses Magma at a Glance