Add optimize thread pool (size 1) dedicated to perform explicit optimize API #3366
Labels
Comments
kimchy
added a commit
that referenced
this issue
Jul 23, 2013
…ize API Have a dedicated thread pool for explicit optimize calls (shard level optimize operations). By default, the size should be 1 to work the same with how things work currently allowing for only 1 shard level optimize on a node. The change allows to see the optimize thread pool stats now, and potentially increase the thread pool size for beefy machines. closes #3366
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…ize API Have a dedicated thread pool for explicit optimize calls (shard level optimize operations). By default, the size should be 1 to work the same with how things work currently allowing for only 1 shard level optimize on a node. The change allows to see the optimize thread pool stats now, and potentially increase the thread pool size for beefy machines. closes elastic#3366
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have a dedicated thread pool for explicit
optimizecalls (shard level optimize operations). By default, the size should be 1 to work the same with how things work currently allowing for only 1 shard level optimize on a node.The change allows to see the optimize thread pool stats now, and potentially increase the thread pool size for beefy machines.
The text was updated successfully, but these errors were encountered: