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/14bb9a8c-5d74-4a0e-a155-1178ce2be25b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
