TESTS: Enable DEBUG Logging in Flaky Test #34091
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and in org.elasticsearch.transport.RemoteClusterConnection.ConnectHandler#collectRemoteNodes
(the sequence of caught error in the last catch block (https://github.com/elastic/elasticsearch/blob/master/server/src/main/java/org/elasticsearch/transport/RemoteClusterConnection.java#L544) and moving on to the next seed node seems to be the only path by which the error logged in RemoteClusterConnectionTests#testCloseWhileConcurrentlyConnecting leaks a connection #33756 (
RuntimeException
without message from a successful connect callback and then subsequent cancellation because closed exception on the same listener) could come about)Can't reproduce the issue in #33756 at all locally (tried 100k+ runs on OSX, Ubuntu and CentOS), but I think this should make it relatively straightforward to track this down.