Unfortunately it would not be enough since there are also merging threads that take CPI and I/O. I would recommend to stick with the defaults and only try to change settings if you observe latency spikes at search time which are due to indexing.
On Tue, Apr 14, 2015 at 3:57 AM, Debayan Banerjee < [email protected]> wrote: > I have a setup where there is occasional heavy indexing but it is critical > to continue serving read requests. Would it then be a good idea to assign > only n-1 cores to index and bulk threadpools (n-1 threadpool size) while > leave one core free for just search? > > -- > > Debayan Banerjee > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAOvawCs%3D89nX06iBUYE4AFw%3D2dTX%2Byjg7qjeoxSHFZNJdGzspQ%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAOvawCs%3D89nX06iBUYE4AFw%3D2dTX%2Byjg7qjeoxSHFZNJdGzspQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adrien -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO5%3DkAhJ_TA%3D2aWAeXPJH-XEX9UH945R2%3DyoqLwwTCmQ8-HAug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
