Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.1.0
-
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
For Gerrit Dashboard: MB-49382 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
168343,15 | MB-49382 (7.1.0 2012) Indexer use cgroups CPU and mem info when enabled | unstable | indexing | Status: MERGED | +2 | +1 |
169179,11 | MB-49382 Part 2 (7.1.0 2103) Make stats, other missed code cgroup-aware | unstable | indexing | Status: MERGED | +2 | +1 |
170906,4 | MB-49382 Part 3 (7.1.0 2284) Fix num_cpu_core indexer stat for cgroups | unstable | indexing | Status: MERGED | +2 | +1 |