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

workload: retry errors when tolerate-errors is set #123305

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

andrewbaptist
Copy link
Collaborator

Previously if tolerate errors was set, the workload would log and drop errors. Now it will retry the errors. This more closely simulates how clients would use our system.

Informs: #123304

Epic: none

Release note: None

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@andrewbaptist andrewbaptist force-pushed the 2024-04-29-tolerate-errors-retry branch 4 times, most recently from f3647df to b3056a4 Compare May 2, 2024 02:21
Previously the limiter would respond to a cluster slowdown by slowing
down its rate if --max-rate was set, and it would never recover the
missed requests. With this change it will save the missed requests in
the limiters burst and issue requests faster after the cluster can go
faster. This turns the --max-rate into a maximum over a longer interval
rather than always starting from now.

As part of this change the workload is ramped up more consistently if
max rate is set by both ramping up the number of workers as well as the
number of requests per second each worker makes. Previously --max-rate
and --ramp did not play well together.

Release note: None
Previously if tolerate errors was set, the workload would log and drop
errors. Now it will retry the errors. This more closely simulates how
clients would use our system.

Informs: cockroachdb#123304

Epic: none

Release note: None
@andrewbaptist andrewbaptist force-pushed the 2024-04-29-tolerate-errors-retry branch from b3056a4 to b646fb7 Compare May 2, 2024 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants