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

[GSI] indexer.settings.max_cpu_percent does not take effect

    XMLWordPrintable

Details

    • Triaged
    • No

    Description

      Code in indexer, plasma and moi currently use the NumCPU() call to determine the number of go routines to spawn for various purposes.

      This NumCPU() call ignores any setting made to GOMAXPROCS either via the environment variable or via the indexer.settings.max_cpu_percent.

      As a result, currently it is not possible to limit the CPU activity of indexer.

      Instead code in indexer, plasma, moi must use GOMAXPROCS(0) instead of NumCPU() so that external attempts to limit the CPU consumption can be honored.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-26307 Improve periodic CPU spikes on indexer nodes during moi disk snapshot persistence

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          For Gerrit Dashboard: MB-30250
          # Subject Branch Project Status CR V
          108701,3 MB-30250 honour max_cpu_percent setting unstable indexing Status: MERGED +2 +1

          Activity

            People

              deepkaran.salooja Deepkaran Salooja
              sundar Sundar Sridharan (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty