-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
add new leader slot metric to track account contention throttling #27654
add new leader slot metric to track account contention throttling #27654
Conversation
@taozhu-chicago this should help in understanding how contentious account locks are in production |
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.
lgtm
@@ -104,6 +104,11 @@ struct LeaderSlotPacketCountMetrics { | |||
// then hit the age limit after failing to be comitted. | |||
executed_transactions_failed_commit_count: u64, | |||
|
|||
// total number of transactions that were excluded from the block because there were concurrent write locks active. | |||
// These transactions are added back to the buffered queue and are already counted in | |||
// `self.retrayble_errored_transaction_count`. |
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.
thanks for clarifying this counter is a subset of retrayble_errored_transaction_count
Problem
it's unclear how much impact attempts to write lock the same account from parallel banking threads on cluster speed has
Summary of Changes
added a metric to trace this in production