tree c3f32122c4e7ec2eb1db9ae0fd831803d5a557a5
parent 8a086925bd82656d84040549cb27216b77a3f05e
author Przemyslaw Waliszewski <pwaliszewski@gmail.com> 1613673576 +0100
committer Przemyslaw Waliszewski <pwaliszewski@gmail.com> 1614023541 +0100

Use dedicated Executor Service for batch indexing

Implement separate flow for batch and interactive indexing on active and
passive node. Introduce new BatchChangeHandler with separate
indexExecutor to split batch and interactive index thread pools.

Splitting interactive and batch indexing will reduce latency of the
interactive indexing events during massive batch indexing tasks. Without
this change there is a huge possibility that an new interactive indexing
event will reach the passive node after batch backlog queue is empty.

Bug: Issue 12500
Change-Id: I4cefa1f5f3c30cf8743bda6f626381f0caa48d2c