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

[CBSE][sigar] Indexer CPU and memory monitoring doesn't work correctly in CPU limited containers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 7.1.0
    • 7.1.0
    • secondary-index, sigar
    • None
    • Untriaged
    • 1
    • Unknown

    Description

      In 7.1 Indexer is adding support for CPU monitoring to adjust mutation processing and scanning if the CPU gets too high. Indexer gets this information from sigar, but sigar returns system information and not container-specific information essentially turning off this capability in CPU-limited containers.

      (
      The related sigar bug IS MB-40464; ns_server: MB-47591; memcached: MB-49632, MB-49867

      This sigar issue is not specific to CPU throttling because GSI uses sigar in other places, including for memory monitoring. Related ns_server CBSEs: CBSE-10794, CBSE-10914, CBSE-10531, CBSE-10845.

      See also MB-36704 on the need to avoid setting GOMAXPROCS to a value higher than the available number of cores (e.g. via UI setting indexer.settings.max_cpu_percent).

      --Kevin Cherkauer
      )

       

       

      Attachments

        Issue Links

          Activity

            People

              girish.benakappa Girish Benakappa
              dfinlay Dave Finlay
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty