I see that ES switch back to ConcurrentMergeScheduler in 1.1.1 due to it
affecting indexing performance in 1.1.0.
https://github.com/elasticsearch/elasticsearch/issues/5817
We're on 1.1.0 and cannot upgrade to 1.1.1 for the time being. Is there a
way to switch it back using the API? I tried the following command, but it
seems to not take.
curl -i -XPUT localhost:9200/_cluster/settings -d '{ "persistent": {
"index.merge.scheduler.type":
"org.elasticsearch.index.merge.scheduler.ConcurrentMergeSchedulerProvider"
} }'
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 52
{"acknowledged":true,"persistent":{},"transient":{}}
It does not seem to be set when I try to re-GET it (and no errors in logs
at DEBUG level or above).
curl -i -XGET localhost:9200/_cluster/settings
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 66
{"persistent":{"threadpool":{"bulk":{"size":"8"}}},"transient":{}}
Am using the wrong way of specifying the scheduler? I also tried just
specifying ConcurrentMergeSchedulerProvider instead of the full class name,
but that didn't work.
Any ideas?
David
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/601a831d-2c8e-4615-b816-435a6d4e4d9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
