Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-55966

CDC: Enforce a minimum history_retention_bytes value of 2GiB

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 7.2.0
    • 7.2.0
    • ns_server
    • None
    • Triaged
    • 0
    • No

    Description

      Identified early in the design of CDC was that there is a minimum amount of history that we can retain, e.g. 1 byte is not realistic, there is some granularity that magma operates with. The real minimum per vbucket is actually 2MiB this occurs because magma will always retain at least 1 "sstable of history", resulting in 2GiB for 1024 vbuckets. This leads to an issue in that any history_retention_bytes value under 2GiB could lead a user to question the systems behaviour. Additionally if we do permit <2GiB the current alerting is misleading, for example if I configure 1GiB of history and 180 seconds of time, the ns_server alert will trigger when my history size is 90% of the 1GiB, but the reality is that magma won't need to "trim" history until 2GiB is exceeded.

      For 7.2 we should set a minimum configuration value of 2GiB and ensure documentation (Tony Hillman) explains why this exists.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jwalker Jim Walker
              jwalker Jim Walker
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty