Jason Tedor 90ab949415

Improve performance of shards limits decider (#53577) ...

On clusters with a large number of shards, the shards limits allocation
decider can exhibit poor performance leading to timeouts applying
cluster state updates. This occurs because for every shard, we do a loop
to count the number of shards on the node, and the number of shards for
the index of the shard. This is roughly quadratic in the number of
shards. This loop is not necessary, since we already have a O(1) method
to count the number of non-relocating shards on a node, and with this
commit we add some infrastructure to RoutingNode to make counting the
number of shards per index O(1).

2020-03-18 20:58:22 -04:00

..

licenses

Upgrade to final lucene 8.5.0 snapshot (#53293)

2020-03-10 09:32:59 +00:00

src

Improve performance of shards limits decider (#53577)

2020-03-18 20:58:22 -04:00

build.gradle

Upgrade to lucene-8.5.0-snapshot-3333ce7da6d (#51749)

2020-01-31 11:20:15 -05:00