Skip to content

Conversation

@original-brownbear
Copy link
Contributor

  • Wait for all Rec. to Stop on Node Close

  • This issue is in the RecoverySourceHandler#acquireStore. If we submit the store release to the generic threadpool while it is getting shut down we never complete the futue we wait on (in the generic pool as well) and fail to ever release the store potentially.

  • Fixed by waiting for all recoveries to end on node close so that we aways have a healthy thread pool here

  • Closes CI UpdateShardAllocationSettingsIT.testUpdateSameHostSetting failure #45956

backport of #46178

* Wait for all Rec. to Stop on Node Close

* This issue is in the `RecoverySourceHandler#acquireStore`. If we submit the store release to the generic threadpool while it is getting shut down we never complete the futue we wait on (in the generic pool as well) and fail to ever release the store potentially.
* Fixed by waiting for all recoveries to end on node close so that we aways have a healthy thread pool here
* Closes elastic#45956
@original-brownbear original-brownbear added backport pending :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. backport and removed backport pending labels Sep 2, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@original-brownbear original-brownbear merged commit 2662c1b into elastic:7.x Sep 2, 2019
@original-brownbear original-brownbear deleted the 46178-7.x branch September 2, 2019 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants