Nhat Nguyen ef5c397c0f

Sending operations concurrently in peer recovery (#58018) ...

Today, we send operations in phase2 of peer recoveries batch by batch
sequentially. Normally that's okay as we should have a fairly small of
operations in phase 2 due to the file-based threshold. However, if
phase1 takes a lot of time and we are actively indexing, then phase2 can
have a lot of operations to replay.

With this change, we will send multiple batches concurrently (defaults
to 1) to reduce the recovery time.

Backport of #58018

2020-07-07 22:03:31 -04:00

..

circuit_breaker.asciidoc

[7.x] [DOCS] Add supported ESS settings to ES docs (#57953) (#58981)

2020-07-02 19:40:45 -04:00

fielddata.asciidoc

[DOCS] Relocate indices module content (#54903) (#57413)

2020-06-01 09:44:32 -04:00

index_management.asciidoc

[7.x] [DOCS] Add supported ESS settings to ES docs (#57953) (#58981)

2020-07-02 19:40:45 -04:00

indexing_buffer.asciidoc

[DOCS] Relocate indices module content (#54903) (#57413)

2020-06-01 09:44:32 -04:00

query_cache.asciidoc

[DOCS] Relocate indices module content (#54903) (#57413)

2020-06-01 09:44:32 -04:00

recovery.asciidoc

Sending operations concurrently in peer recovery (#58018)

2020-07-07 22:03:31 -04:00

request_cache.asciidoc

[DOCS] Relocate indices module content (#54903) (#57413)

2020-06-01 09:44:32 -04:00

search-settings.asciidoc

[DOCS] Relocate indices module content (#54903) (#57413)

2020-06-01 09:44:32 -04:00