Remove transaction retry functionality from Access RPC backend #8043
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.
Remove transaction retry functionality from Access RPC backend
Closes: #7632
Summary
Removed the transaction retry mechanism from the Access RPC backend. This feature was designed to automatically retry transactions that were successfully sent to collection nodes but never finalized. According to the issue discussion, this feature has never been used on public Access nodes and contains technical debt that would need fixing before it could be safely deployed.
Changes:
retrier
package (engine/access/rpc/backend/transactions/retrier/
)RetryEnabled
parameter from backend configurationretry-enabled
CLI flag from access node builderRegisterTransaction
andProcessFinalizedBlockHeight
methods from transactions backendReview & Testing Checklist for Human
--retry-enabled
flag was never set totrue
in any production access node deployments (check node configs and deployment scripts)ProcessFinalizedBlockHeight
from the finalization callback doesn't break any other functionality that depended on itTesting Plan
Since this feature was reportedly never enabled in production:
Notes