Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MultiIteratorScanner - check read-locks #28853

Closed
apfitzge opened this issue Nov 17, 2022 · 0 comments · Fixed by #28862
Closed

MultiIteratorScanner - check read-locks #28853

apfitzge opened this issue Nov 17, 2022 · 0 comments · Fixed by #28862
Assignees
@apfitzge
Labels
validator Issues that relate to the validator

Comments

@apfitzge
Copy link
Contributor

Problem

Currently the should_process function passed to the MultiIteratorScanner only considers write-locks for accounts. It should consider read-locks in order to make sure we don't create conflicting batches.

Proposed Solution

Add read-locks to the should_process function used by MultiIteratorScanner
@apfitzge apfitzge added the validator Issues that relate to the validator label Nov 17, 2022
@apfitzge apfitzge self-assigned this Nov 17, 2022
@apfitzge apfitzge mentioned this issue Nov 17, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@apfitzge apfitzge

Labels
validator Issues that relate to the validator
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/multi-iterator-scanner-read-locks apfitzge/agave
1 participant
@apfitzge