-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issue 3070 - Wait for state store commits to finish based on logs #3063
Merged
patchwork01
merged 52 commits into
develop
from
3060-measure-deployed-state-store-committer-throughput
Aug 14, 2024
Merged
Changes from 17 commits
Commits
Show all changes
52 commits
Select commit
Hold shift + click to select a range
c11b404
Set up StateStoreCommitterST
patchwork01 3a27409
Refactor StateStoreCommitRequest to hold table ID
patchwork01 e8175a7
Move reading from S3 into StateStoreCommitRequestDeserialiser
patchwork01 b9df6d6
Assert on StateStoreCommitRequest.getTableId
patchwork01 47183ef
Merge branch '3061-send-commits-in-parallel' into 3060-measure-deploy…
patchwork01 409c426
Add missing Javadoc
patchwork01 1ad62d8
Merge branch 'develop' into 3060-measure-deployed-state-store-committ…
patchwork01 08b4b14
Merge branch 'develop' into 3060-measure-deployed-state-store-committ…
patchwork01 a2a0706
Rename methods to apply commit requests
patchwork01 71ee3aa
Adjust state store committer logs
patchwork01 0c9f094
Wait for state store commits in-memory
patchwork01 5422fdc
Add StateStoreCommitterRunsBuilder
patchwork01 72b487e
Read state store commit applied event
patchwork01 6206a31
Test reading unrecognised log
patchwork01 8bf2804
Read logs in AwsStateStoreCommitterDriver
patchwork01 adb98ec
Fix reading log with fields in reverse order
patchwork01 6a73294
Test ignoring extra log fields
patchwork01 d2b2b18
Add comments to StateStoreCommitterLogEntry
patchwork01 a263ba2
Use named log groups in StateStoreCommitterLogEntry
patchwork01 4b8eb46
Use constants for capture groups
patchwork01 35f7b52
Replace "capture group" with "capturing group"
patchwork01 44fe0a6
Load from S3 in AwsStateStoreCommitterDriverIT
patchwork01 eda8212
Test building unfinished runs
patchwork01 769bdd4
Fix wait for commit
patchwork01 24a4e67
Fix SystemTestStateStoreFakeCommitsTest
patchwork01 1a51d62
Unit test decrementWaitForNumCommits
patchwork01 1dbe546
Handle unknown run times
patchwork01 197f831
Add slack & logging in query for committer runs
patchwork01 f35b7cb
Grant reading state store committer logs
patchwork01 8c1cdc0
Apply query time slack to end time
patchwork01 59cfead
Reduce slack for quering committer runs
patchwork01 b3bdc33
Introduce StateStoreCommitterLogEntry
patchwork01 ded3048
Remove StateStoreCommitterRun from in-memory implementation
patchwork01 5ee106d
Rename ReadStateStoreCommitterLogs
patchwork01 1bdb0bf
Remove StateStoreCommitterRun
patchwork01 8f61246
Use StateStoreCommitterLogEntry.getLastTime
patchwork01 d9f53d0
Test logs processing in WaitForStateStoreCommits
patchwork01 0a69a1e
Refactor WaitForStateStoreCommits
patchwork01 93b900c
Remove unused logger
patchwork01 9e2232a
Remove unused code
patchwork01 ad89a13
Remove extra helper from ReadStateStoreCommitterLogsTest
patchwork01 8c6b58e
Remove unused method
patchwork01 c4b8b6f
Remove unused logger
patchwork01 74c49b7
Fix SystemTestStateStoreFakeCommitsTest
patchwork01 8807267
Set skipRust property in deployTest.sh
patchwork01 05d6366
Grant StartQuery/GetQueryResults for log stream
patchwork01 c508571
Handle new line at end of log message
patchwork01 c19975b
Adjust assertions in StateStoreCommitterST
patchwork01 b2795a8
Rename WaitForStateStoreCommitLogs
patchwork01 ca9b8f1
Ignore file update time in assertion
patchwork01 3064b36
Adjust assertion on files
patchwork01 48958ad
Use long for record count in assertion
patchwork01 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Any reason for the re-ordering of the case statements?
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.
I felt like the stored in S3 type should be separate from the others because it's handled differently. I'm not sure there's a good way to make this clear though.