-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
admission: incorporate higher compaction rate during WAL failover #138708
Conversation
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 commit is from #138699
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @aadityasondhi)
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.
Reviewable status: complete! 1 of 0 LGTMs obtained
5aa052a
to
5466228
Compare
TFTR! |
|
bors r=aadityasondhi |
138708: admission: incorporate higher compaction rate during WAL failover r=aadityasondhi a=sumeerbhola WAL failover can happen even when the throughput sustainable by the primary is high (since we tune WAL failover to happen at a 100ms latency threshold). So if the workload increase is resulting in more compactions, we should incorporate that into the tokens given out by the ioLoadListener. Informs #138655 Epic: none Release note: None Co-authored-by: sumeerbhola <[email protected]>
Build failed: |
WAL failover can happen even when the throughput sustainable by the primary is high (since we tune WAL failover to happen at a 100ms latency threshold). So if the workload increase is resulting in more compactions, we should incorporate that into the tokens given out by the ioLoadListener. Informs cockroachdb#138655 Epic: none Release note: None
5466228
to
e423f3e
Compare
bors r=aadityasondhi |
Build succeeded: |
WAL failover can happen even when the throughput sustainable by the primary
is high (since we tune WAL failover to happen at a 100ms latency threshold).
So if the workload increase is resulting in more compactions, we should
incorporate that into the tokens given out by the ioLoadListener.
Informs #138655
Epic: none
Release note: None