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.

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

[4.0 -> main] Use block_num for interrupt of start_block & Use single timer for read and write windows #910

Merged
merged 9 commits into from
Mar 27, 2023

Conversation

heifner
Copy link
Member

@heifner heifner commented Mar 27, 2023

Signal received block with the block number so that start_block can be interrupted even if the block is received before the start of start_block. This is particularly important for #867, but also useful as mitigation against race condition of receiving block right before start of the block in current implementation. See #648.

Includes PR: Use a single timer for read and write windows
Read window and write window run exclusively with each other; they do not run at the same time. A single timer is sufficient to control them and makes code simpler.

Merges #893 & #908 & #905 into main.
See #824 for #905
Resolves #891

@heifner heifner changed the title [4.0 -> main] Use block_num for interrupt of start_block [4.0 -> main] Use block_num for interrupt of start_block & Use single timer for read and write windows Mar 27, 2023
@heifner heifner requested review from greg7mdp and linh2931 March 27, 2023 18:56
@heifner heifner merged commit 1c5e133 into main Mar 27, 2023
@heifner heifner deleted the GH-891-interrupt-start-block-main branch March 27, 2023 19:38
@heifner heifner added the OCI Work exclusive to OCI team label Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCI Work exclusive to OCI team
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Interrupt start block when blocks ready to process
3 participants