Execute blackhole response on correct transport#92312
Merged
elasticsearchmachine merged 3 commits intoelastic:mainfrom Dec 13, 2022
Merged
Execute blackhole response on correct transport#92312elasticsearchmachine merged 3 commits intoelastic:mainfrom
elasticsearchmachine merged 3 commits intoelastic:mainfrom
Conversation
We simulate sending traffic along a blackholed connection with a disconnection exception that we withold until far into the future. Today this exception is delivered using the transport of the responding node, but it should be the requesting node. This commit fixes that. Not sure how this _ever_ worked, but we made things stricter in elastic#92245 and that meant this bug led to test failures. Closes elastic#92307
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
DaveCTurner
commented
Dec 12, 2022
| protected void onDisconnectedDuringSend(long requestId, String action, DisruptableMockTransport destinationTransport) { | ||
| destinationTransport.execute(getDisconnectException(requestId, action, destinationTransport.getLocalNode())); | ||
| private void onDisconnectedDuringSend(long requestId, String action, DisruptableMockTransport destinationTransport) { | ||
| execute(getDisconnectException(requestId, action, destinationTransport.getLocalNode())); |
Member
Author
There was a problem hiding this comment.
This line is the fix, everything else is just noise. Looks simple, but wow this took hours to pin down.
| deterministicTaskQueue.runAllRunnableTasks(); | ||
|
|
||
| assertTrue(responseHandlerReleased.get()); | ||
| assertTrue(rebootedNodes.contains(node1) || responseHandlerCalled.get()); |
Member
Author
There was a problem hiding this comment.
This assertion shows the problem.
idegtiarenko
approved these changes
Dec 13, 2022
pxsalehi
approved these changes
Dec 13, 2022
Member
Author
|
@elasticmachine update branch |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Dec 13, 2022
We simulate sending traffic along a blackholed connection with a disconnection exception that we withold until far into the future. Today this exception is delivered using the transport of the responding node, but it should be the requesting node. This commit fixes that. Not sure how this _ever_ worked, but we made things stricter in elastic#92245 and that meant this bug led to test failures. Closes elastic#92307
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 13, 2022
We simulate sending traffic along a blackholed connection with a disconnection exception that we withold until far into the future. Today this exception is delivered using the transport of the responding node, but it should be the requesting node. This commit fixes that. Not sure how this _ever_ worked, but we made things stricter in #92245 and that meant this bug led to test failures. Closes #92307
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
We simulate sending traffic along a blackholed connection with a disconnection exception that we withold until far into the future. Today this exception is delivered using the transport of the responding node, but it should be the requesting node. This commit fixes that.
Not sure how this ever worked, but we made things stricter in #92245 and that meant this bug led to test failures.
Closes #92307