Ahh, got it. Thanks.
On Saturday, April 19, 2014 10:05:39 AM UTC-4, Jörg Prante wrote:
>
> No, you can not change the merge scheduler settings via API. Threadpool
> settings updating works.
>
> Jörg
>
>
> On Sat, Apr 19, 2014 at 3:22 PM, David Smith
> > wrote:
>
>> Thanks, Jörg. Is it possible t
No, you can not change the merge scheduler settings via API. Threadpool
settings updating works.
Jörg
On Sat, Apr 19, 2014 at 3:22 PM, David Smith wrote:
> Thanks, Jörg. Is it possible to set these via API instead of changing the
> yaml?
>
> --
> You received this message because you are subscr
Thanks, Jörg. Is it possible to set these via API instead of changing the
yaml?
--
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...@googl
I use this on 1.1.0 in my config/elasticsearch.yml
index:
merge:
scheduler:
type: concurrent
max_thread_count: 4
policy:
type: tiered
max_merged_segment: 1gb
segments_per_tier: 4
max_merge_at_once: 4
max_merge_at_once_explicit: 4
threa
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
