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
Cannot change index.queue_size #38907
Comments
Did you indeed set this only on your ingest nodes? The relevant place is the data nodes, where the bulk shard requests are actually executed on the bulk thread pool. All appears to be well, otherwise:
And then:
|
@jasontedor I assumed the error was propagating from the ingest nodes... I'll reboot the data nodes and see if the issue persists... 😶 |
No, you can see that in the exception message:
It's a remote transport exception happening on |
@jasontedor ++ yeah thanks my bad |
No worries! |
Description
I want to increase the queue capacity for my ingest nodes, but I'm seeing different things in the docs:
So setting both
thread_pool.index.queue_size: 500
andthread_pool.write.queue_size: 500
I still get logs sayingqueue capacity = 200
.These are running on beefy boxes, and according to monitoring via Kibana are showing 3% CPU utilization and 50% JVM memory. I don't want to scale horizontally until these are better utilized.
What's going on here?
Elasticsearch version (
bin/elasticsearch --version
):OS version (
uname -a
if on a Unix-like system):Description of the problem including expected versus actual behavior:
I set the
thread_pool.index.queue_size
according to the doc example https://www.elastic.co/guide/en/elasticsearch/reference/6.5/modules-threadpool.html#typesSteps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
thread_pool.index.queue_size: 500
thread_pool.write.queue_size: 500
queued tasks = 200
Provide logs (if relevant):
Deprecated?
Full elasticsearch.yml:
The text was updated successfully, but these errors were encountered: