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

set vreplication net read and net write timeout session vars to high values #14203

Merged

Conversation

olyazavr
Copy link
Contributor

@olyazavr olyazavr commented Oct 6, 2023

Description

On some particularly busy tables, we cannot run vitess onlineddl schema changes because it fails with unexpected EOF\nio.ReadFull(packet body of length 287) failed (errno 2013) (sqlstate HY000). Note that ghost also fails on these tables, but we have higher hopes for vitess.

In several slack threads, the recommendation was to increase net_read_timeout (default is 30, recommended for vreplication is 300) and net_write_timeout (default is 60, recommended for vreplication is 600). However, we don't want to modify these values globally, would be nice if only vreplication's session had these higher values - and this PR does just that

Update: with these changes, we were able to successfully run onlineddl schema changes on an incredibly busy table that was previously unable to run any kind of migrations

Related Issue(s)

Fixes #14202

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

@vitess-bot
Copy link
Contributor

vitess-bot bot commented Oct 6, 2023

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Oct 6, 2023
@github-actions github-actions bot added this to the v19.0.0 milestone Oct 6, 2023
Signed-off-by: Olga Shestopalova <[email protected]>
@rohit-nayak-ps rohit-nayak-ps added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: VReplication and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request labels Oct 10, 2023
@@ -60,6 +60,8 @@ const (
getAutoIncrementStep = "select @@session.auto_increment_increment"
setSessionTZ = "set @@session.time_zone = '+00:00'"
setNames = "set names 'binary'"
setNetReadTimeout = "set @@session.net_read_timeout = 300"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We were discussing this yesterday and the consensus was that we should not hardcode values since the actual value might vary based on the cluster environment.

We can add flags for this as common vttablet flags similar to the query timeout PR. Your values seem fine as defaults to me.

Olga Shestopalova added 3 commits October 10, 2023 15:11
Signed-off-by: Olga Shestopalova <[email protected]>
Signed-off-by: Olga Shestopalova <[email protected]>
Copy link
Contributor

@rohit-nayak-ps rohit-nayak-ps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@rohit-nayak-ps rohit-nayak-ps merged commit 6953390 into vitessio:main Oct 11, 2023
115 checks passed
pjambet pushed a commit to Shopify/vitess that referenced this pull request Nov 8, 2023
…values (vitessio#14203)

Signed-off-by: Olga Shestopalova <[email protected]>
Co-authored-by: Olga Shestopalova <[email protected]>
pawandubey pushed a commit to Shopify/vitess that referenced this pull request Apr 5, 2024
…values (vitessio#14203)

Signed-off-by: Olga Shestopalova <[email protected]>
Co-authored-by: Olga Shestopalova <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: VReplication Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
3 participants