forked from solana-labs/solana
-
Notifications
You must be signed in to change notification settings - Fork 1k
add retries to transaction sending in LocalCluster #1747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
yihau
merged 1 commit into
anza-xyz:master
from
gregcusack:add-retry-to-local-cluster-tests
Jun 17, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this part is similar to thin_client and I think it is closer to the original behavior which before we switched to QuicTpuClient.
agave/thin-client/src/thin_client.rs
Lines 214 to 261 in a5229f9
I'm a little bit confused why it compares
MAX_PROCESSING_AGEwithnow.elapsed().as_secs()but I think we can update this one in different PR!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Valid concern. The idea of the original code is that if we waited longer than
MAX_PROCESSING_AGEit means that the blockhash has expired so we must update blockhash and resign which might a desired behavior for production applications.Yet I'm concerned about using this code for integration tests since in the worst case scenario we can wait for minutes for transaction to be delivered, not sure if it worth it or better to accept failure if we cannot send within several leader slots (opposite to hundreds).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think yihau's point was that
MAX_PROCESSING_AGEhas a unit of slots, not seconds. So the code waits more than twice as long as necessary.