Sebastian Röbke
Sebastian Röbke
Related: - https://github.com/Graylog2/collector-sidecar/issues/432
Related: https://github.com/Graylog2/collector-sidecar/issues/426
Related: https://github.com/Graylog2/graylog2-server/issues/5062
Hi @servo1x, we would welcome a PR that implements this, but unfortunately we don’t have much time to work on it ourselves at the moment.
For reference, there was an attempt to add such a counter to kubelet, but closed in favour of adding it to the container runtime: https://github.com/kubernetes/kubernetes/pull/87856
Using heartbeats should be fine for us. We just turned it off by default, but some clients are already using the feature.
Hi @ryan-carroll-graylog, thanks for working on this! I removed myself as a reviewer – this should better be done by the engineers.
@todvora In the graphs you posted, does `10 threads, forcemerge enabled` mean `elasticsearch_index_optimization_jobs = 10` while `elasticsearch_max_total_connections_per_route = 20` ?
The solution is to set `elasticsearch_index_optimization_jobs` lower than `elasticsearch_max_total_connections_per_route`. This can be done in the server config. For example: - `elasticsearch_max_total_connections = 200` (Graylog's default value) - `elasticsearch_max_total_connections_per_route = 20`...
@tellistone Yes, I think the default for `elasticsearch_index_optimization_jobs` should be changed to `10`. @todvora Since you are assigned this this ticket, could you take care of this?