Repository navigation
api: replace the executor client on any transport error - #29
Merged
Merged
Conversation
The Thrift concurrent client marks itself bad (stop_ set for good) on any receive error, but the node replaced it only on NOT_OPEN, that is when the next call had already failed. One timeout or dropped connection therefore failed the following contract call too, on this node only, and a late reply to a timed-out call could still arrive on the old connection. Replace the client on every TTransportException; the watcher reconnects as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The Thrift concurrent client marks itself bad (stop_ set for good) on any
receive error, but the node replaced it only on NOT_OPEN, that is when the
next call had already failed. One timeout or dropped connection therefore
failed the following contract call too, on this node only, and a late reply
to a timed-out call could still arrive on the old connection. Replace the
client on every TTransportException; the watcher reconnects as before.
Testing
test/phase1-combined(all node fixes) with mixed executors (executor_ref=test/compatible-fixes): 17 of 17 contract calls returned the expected value across the restart test,CounterandLedgerstates equal on all 7 nodes, state digests equal up to sequence 1100.Compatible: no result of a valid contract call changes, so nodes can adopt it one by one.
🤖 Generated with Claude Code