You could set up a special node for "low priority" search, with "slim" thread pool settings, and forward client calls to it respectively.
Jörg On Mon, Mar 24, 2014 at 3:08 PM, Paweł Młynarczyk <[email protected]> wrote: > There are many users working with the application. Some of them are online > users, that should have their requests served in real time and some of them > are workers that are preparing reports and their requests can wait. At the > moment, all the requests arriving to elasticsearch are queued at the same > queue and that sometimes results in online users not getting their request > served as soon as possible or even getting rejected when the queue is full > of workers' requests. That could be solved by adding separate Thread Pool > and Queue for 'low priority search'. Same would apply for other operations > (get, bulk etc). > > Are there any plans or any chance for this kind of feature being > implemented in Elasticsearch? > > -- -- 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/CAKdsXoGbX3rQ6HEU2pzSKYpQhkm6Pe%3Dke%2B7qDAj%3DL-DfyMfyDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
