-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename the bulk thread pool to write thread pool #29593
Conversation
This commit renames the bulk thread pool to the write thread pool. This is to better reflect the fact that the underlying thread pool is used to execute any document write request (single-document index/delete/update requests, and bulk requests). With this change, we add support for fallback settings thread_pool.bulk.* which will be supported until 7.0.0. We also add a system property so that the display name of the thread pool remains as "bulk" if needed to avoid breaking users.
Pinging @elastic/es-core-infra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
`thread_pool.write.size` and `thread_pool.write.queue_size`, respectively. The | ||
fallback settings will be removed in 7.0.0. Additionally, this means that some | ||
APIs (e.g., the node stats API) will now display the name of this thread pool as | ||
`write`. If this is change impacts you (e.g., for monitoring that you have in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: is change
-> change
fallbackSizeSetting, | ||
s -> Setting.parseInt(s, 1, applyHardSizeLimit(settings, name), sizeKey), | ||
properties); | ||
this.fallbackSizeSetting = fallbackSizeSetting; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: this could be set above instead of creating a local?
fallbackQueueSizeSetting, | ||
s -> Setting.parseInt(s, Integer.MIN_VALUE, queueSizeKey), | ||
properties); | ||
this.fallbackQueueSizeSetting = fallbackQueueSizeSetting; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
`bulk`:: | ||
For bulk operations. Thread pool type is `fixed` | ||
`write`:: | ||
For write operations. Thread pool type is `fixed` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's be more explicit, eg. "index and bulk"?
@@ -69,7 +69,7 @@ | |||
public static final String GET = "get"; | |||
public static final String ANALYZE = "analyze"; | |||
public static final String INDEX = "index"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
silly question (only looking at the diff I don't have full context), do we need to keep this constant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jpountz Yes; this is in 6.x where the index
thread pool remains.
@@ -55,7 +55,7 @@ protected Settings nodeSettings(int nodeOrdinal) { | |||
//.put("thread_pool.listener.queue_size", 1) | |||
.put("thread_pool.get.queue_size", 1) | |||
// default is 50 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick, but can we update this to 200 too (or remove the comment?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pushed bec9592.
This commit renames the bulk thread pool to the write thread pool. This is to better reflect the fact that the underlying thread pool is used to execute any document write request (single-document index/delete/update requests, and bulk requests). With this change, we add support for fallback settings thread_pool.bulk.* which will be supported until 7.0.0. We also add a system property so that the display name of the thread pool remains as "bulk" if needed to avoid breaking users.
* master: (21 commits) Remove bulk fallback for write thread pool (elastic#29609) Fix an incorrect reference to 'zero_terms_docs' in match_phrase queries. Update the version compatibility for zero_terms_query in match_phrase. Account translog location to ram usage in version map Remove extra spaces from changelog Add support to match_phrase query for zero_terms_query. (elastic#29598) Fix incorrect references to 'zero_terms_docs' in query parsing error messages. (elastic#29599) Build: Move java home checks to pre-execution phase (elastic#29548) Avoid side-effect in VersionMap when assertion enabled (elastic#29585) [Tests] Remove accidental logger usage Add tests for ranking evaluation with aliases (elastic#29452) Deprecate use of `htmlStrip` as name for HtmlStripCharFilter (elastic#27429) Update plan for the removal of mapping types. (elastic#29586) [Docs] Add rankEval method for Jva HL client Make ranking evaluation details accessible for client Rename the bulk thread pool to write thread pool (elastic#29593) [Test] Minor changes to rank_eval tests (elastic#29577) Fix missing node id prefix in startup logs (elastic#29534) Added painless execute api. (elastic#29164) test: also assert deprecation warning after clusters have been closed. ...
* es/6.x: (28 commits) TEST: Unmute testPrimaryRelocationWhileIndexing Never leave stale delete tombstones in version map (#29619) Do not serialize common stats flags using ordinal (#29600) Remove stale comment from JVM stats (#29625) TEST: Mute testPrimaryRelocationWhileIndexing Remove 7.0.0 from 6.x changelog (#29621) Add support to match_phrase query for zero_terms_query. (#29598) Account translog location to ram usage in version map Avoid side-effect in VersionMap when assertion enabled (#29585) Build: Move java home checks to pre-execution phase (#29548) Add tests for ranking evaluation with aliases (#29452) [Test] Fix assertion in SearchDocumentationIT Deprecate use of `htmlStrip` as name for HtmlStripCharFilter (#27429) test: Assert deprecated http.enebled setting warning Update plan for the removal of mapping types. (#29586) [Docs] Add rankEval method for Jva HL client Make ranking evaluation details accessible for client Rename the bulk thread pool to write thread pool (#29593) [Test] Minor changes to rank_eval tests (#29577) test: Assert deprecated http.enebled setting warning ...
This change also broke the nodes stats API since there is no bulk threadpool anymore. So all metrics and alerting tools which used this information is now broken in a minor version upgrade of Elasticsearch. Yes, it's mentioned but still, in a minor? |
Gah, note to self: don't write comments when you're annoyed. There is a workaround mentioned in the linked site. |
Bulk threadpool was renamed to index. See elastic/elasticsearch#29593
Bulk threadpool was renamed to index. See elastic/elasticsearch#29593
This commit renames the bulk thread pool to the write thread pool. This is to better reflect the fact that the underlying thread pool is used to execute any document write request (single-document index/delete/update requests, and bulk requests).
With this change, we add support for fallback settings
thread_pool.bulk.*
which will be supported until 7.0.0.We also add a system property so that the display name of the thread pool remains as "
bulk
" if needed to avoid breaking users.