Bug 1883719
Summary: | Alert ElasticsearchBulkRequestsRejectionJumps never gets pending/firing due to there is no `bulk` thread pool. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Qiaoling Tang <qitang> |
Component: | Logging | Assignee: | Lukas Vlcek <lvlcek> |
Status: | CLOSED ERRATA | QA Contact: | Qiaoling Tang <qitang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.6 | CC: | aos-bugs, brejones, jcantril, lvlcek, periklis |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | logging-exploration | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 11:21:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1888393 |
Description
Qiaoling Tang
2020-09-30 01:12:12 UTC
Target 4.7 as this is not a release blocker Bulk statistics is part of `index` threadpool now. See https://www.elastic.co/guide/en/elasticsearch/reference/6.8/modules-threadpool.html We need to update both the rules and alerts: - https://github.com/openshift/elasticsearch-operator/blob/master/files/prometheus_rules.yml - https://github.com/openshift/elasticsearch-operator/blob/master/files/prometheus_rules.yml Ooops... We need to update both the rules and alerts: - https://github.com/openshift/elasticsearch-operator/blob/master/files/prometheus_rules.yml - https://github.com/openshift/elasticsearch-operator/blob/master/files/prometheus_alerts.yml Tested with elasticsearch-operator.4.6.0-202010081538.p0, the rules are changed to: - name: logging_elasticsearch.rules rules: - expr: | rate(es_threadpool_threads_count{name="index", type="rejected"}[2m]) record: indexing:rejected_requests:rate2m - expr: | rate(es_threadpool_threads_count{name="index", type="completed"}[2m]) record: indexing:completed_requests:rate2m - expr: | sum by (cluster, instance, node) (indexing:rejected_requests:rate2m) / on (cluster, instance, node) (indexing:completed_requests:rate2m) record: indexing:reject_ratio:rate2m Hi @Lukas, I have some doubts: why do we use `es_threadpool_threads_count{name="index", type="rejected"}` and `es_threadpool_threads_count{name="index", type="completed"}` here? I checked the elasticsearch doc(https://www.elastic.co/guide/en/elasticsearch/reference/6.8/modules-threadpool.html), it says `index For index/delete operations. Thread pool type is fixed with a size of # of available processors, queue_size of 200. The maximum size for this pool is 1 + # of available processors.` Besides, in the pr https://github.com/elastic/elasticsearch/pull/29593, it seems the bulk thread pool has been renamed to write thread pool. Am I misunderstanding? You are absolutely correct @Qiaoling Tang Great catch !!! I pushed a new PR to fix this https://github.com/openshift/elasticsearch-operator/pull/533 Verified with quay.io/openshift/origin-elasticsearch-operator@sha256:7cc642127d98d7e63baa5a7ae61a31c87e27f16c8bf0f84387852eb9032e526c Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Errata Advisory for Openshift Logging 5.0.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:0652 |