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

Slack vitess r14.0.5 dsdefense throttle only if lag #170

Conversation

ejortegau
Copy link
Collaborator

@ejortegau ejortegau commented Dec 6, 2023

Description

This PR adds an additional condition to be checked before the Transaction Throttler throttles a request. The condition in question is that the max, most recently seen lag in the shard in the replicas being watched, must be above the configured target replication lag. If that's not the case, throttling does not take place.

This addresses the issue mentioned here.

timvaillancourt and others added 3 commits November 9, 2023 19:04
* make column resolution closer to mysql

Signed-off-by: Andres Taylor <[email protected]>

* Fix bad merge conflict fix

Signed-off-by: Tim Vaillancourt <[email protected]>

* Possible horizon_planning.go fix

Signed-off-by: Tim Vaillancourt <[email protected]>

* Fix aggr_cases.json plan

Signed-off-by: Tim Vaillancourt <[email protected]>

* Fix group by order

Signed-off-by: Tim Vaillancourt <[email protected]>

* Remove 'TablesUsed', not in v14

Signed-off-by: Tim Vaillancourt <[email protected]>

---------

Signed-off-by: Andres Taylor <[email protected]>
Signed-off-by: Tim Vaillancourt <[email protected]>
Co-authored-by: Andres Taylor <[email protected]>
@ejortegau ejortegau marked this pull request as ready for review December 7, 2023 12:53
@ejortegau ejortegau requested a review from a team as a code owner December 7, 2023 12:53
@timvaillancourt
Copy link
Member

timvaillancourt commented Dec 8, 2023

@ejortegau I had a thought, does this overlap with the replication lag cache from go/vt/throttle, and could that code be adapted (and made public) so that logic is reused? 🤔

Copy link

github-actions bot commented Jan 8, 2024

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Jan 8, 2024
Copy link

This PR was closed because it has been stale for 7 days with no activity.

@github-actions github-actions bot closed this Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants