mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
4c68382065
We sometimes see a `ShardLockObtainFailedException` when a shard failed to shut down as fast as we expected, often because a node left and rejoined the cluster. Sometimes this is because it was held open by ongoing scrolls or PITs, but other times it may be because the shutdown process itself is too slow. With this commit we add the ability to capture and log a thread dump at the time of the failure to give us more information about where the shutdown process might be running slowly. Relates #93226 |
||
|---|---|---|
| .. | ||
| cluster | ||
| discovery | ||
| indices | ||
| network | ||
| cluster.asciidoc | ||
| discovery.asciidoc | ||
| gateway.asciidoc | ||
| http.asciidoc | ||
| network.asciidoc | ||
| node.asciidoc | ||
| plugins.asciidoc | ||
| remote-clusters-shared.asciidoc | ||
| remote-clusters.asciidoc | ||
| threadpool.asciidoc | ||
| transport.asciidoc | ||