-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Feature/multi-iterator-scanner-read-locks #28862
Feature/multi-iterator-scanner-read-locks #28862
Conversation
} | ||
|
||
/// Check if a sanitized message's account locks are available. | ||
fn check_sanitized_message_account_locks(&self, message: &SanitizedMessage) -> bool { |
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.
Considering a follow-up change here. We really only need to check the non-static (loaded from lookup) here.
71ecfc6
to
84ae0f0
Compare
84ae0f0
to
31129bf
Compare
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.
First round looks good to add read lock in processing decision making.
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
Problem
consume_scan_should_process_packet doesn't consider read-locks
Summary of Changes
Consider read-locks, also wrap in a struct so these checks are simpler
Fixes #28853