Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-3436

Re-use cluster.queryServiceMemoryQuota

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 2.7.0
    • None
    • None
    • 9 - Cataclysm
    • 2

    Description

      Just realised that we already have couchbaseclusters.spec.cluster.queryServiceMemoryQuota, which does nothing to Couchbase Server (as there was no previous option to set a per-node quota), but is used to determine Pod resource requirements.

      I think the right thing to do here is to keep the existing spec.cluster.queryServiceMemoryQuota and use that value to set queryNodeQuota in 7.6+ (as well as for determining Pod resource requirements), and to remove spec.cluster.query.NodeQuota.

      Given that we're now presenting it as a top-level cluster setting in the 7.6 docs, I think it makes sense to have a single top-level quota value for the Query Service - having both will cause confusion (and possibly issues if they are set to wildly different values).

      Attachments

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

        Activity

          People

            usamah.jassat Usamah Jassat
            justin.ashworth Justin Ashworth
            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