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

MySQL errors: ERInnodbIndexCorrupt #16851

Merged

Conversation

shlomi-noach
Copy link
Contributor

Description

Add ERInnodbIndexCorrupt (error 1817) to the list of known MySQL errors. This can be used in the future to recognize terminal ApplySchema or Online DDL scenarios.

Related Issue(s)

none

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

@shlomi-noach shlomi-noach added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: General Changes throughout the code base labels Sep 26, 2024
Copy link
Contributor

vitess-bot bot commented Sep 26, 2024

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 NeedsBackportReason If backport labels have been applied to a PR, a justification is required 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 Sep 26, 2024
@shlomi-noach shlomi-noach requested a review from a team September 26, 2024 13:06
@shlomi-noach shlomi-noach 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 NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Sep 26, 2024
Copy link

codecov bot commented Sep 26, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 69.43%. Comparing base (4058966) to head (82364b2).
Report is 21 commits behind head on main.

Files with missing lines Patch % Lines
go/vt/vttablet/tabletserver/tabletserver.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #16851      +/-   ##
==========================================
- Coverage   69.44%   69.43%   -0.01%     
==========================================
  Files        1571     1571              
  Lines      202996   203086      +90     
==========================================
+ Hits       140977   141020      +43     
- Misses      62019    62066      +47     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@harshit-gangal harshit-gangal left a comment

Choose a reason for hiding this comment

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

We should use this in
go/vt/vttablet/tabletserver/tabletserver.go to convert from mysql error code to vitess error.

method: convertErrorCode

Signed-off-by: Shlomi Noach <[email protected]>
@shlomi-noach
Copy link
Contributor Author

We should use this in convertErrorCode

@harshit-gangal done.

Comment on lines -1603 to 1605
sqlerror.ErNoReferencedRow2, sqlerror.ERWarnDataOutOfRange:
sqlerror.ErNoReferencedRow2, sqlerror.ERWarnDataOutOfRange, sqlerror.ERInnodbIndexCorrupt:
errCode = vtrpcpb.Code_FAILED_PRECONDITION
case sqlerror.EROptionPreventsStatement:
Copy link
Member

Choose a reason for hiding this comment

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

This got added under Internal Error in constants but used as Failed_Precondition.

// internal
	ERInternalError = ErrorCode(1815)
	ERInternalError      = ErrorCode(1815)
	ERInnodbIndexCorrupt = ErrorCode(1817)

We should align them.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We should align them.

Done.

Signed-off-by: Shlomi Noach <[email protected]>
@shlomi-noach shlomi-noach dismissed harshit-gangal’s stale review October 6, 2024 07:09

concerns have been addressed

@shlomi-noach shlomi-noach merged commit 246caf0 into vitessio:main Oct 6, 2024
98 checks passed
@shlomi-noach shlomi-noach deleted the mysql-err-innodb-index-corrupt branch October 6, 2024 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: General Changes throughout the code base Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants