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

ddl: fix ingest job panic when reset engine failed #53754

Merged
merged 3 commits into from
Jun 4, 2024

Conversation

tangenta
Copy link
Contributor

@tangenta tangenta commented Jun 3, 2024

What problem does this PR solve?

Issue Number: close #53679

Problem Summary:

ei.closedEngine should be empty unless all data has been written and all writers have been closed.

What changed and how does it work?

Use correct closedEngine.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-triage-completed release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 3, 2024
Copy link

tiprow bot commented Jun 3, 2024

Hi @tangenta. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jun 3, 2024
Copy link

codecov bot commented Jun 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.9347%. Comparing base (073f746) to head (292aa53).
Report is 9 commits behind head on master.

Additional details and impacted files
@@                Coverage Diff                @@
##             master     #53754         +/-   ##
=================================================
- Coverage   72.4954%   55.9347%   -16.5607%     
=================================================
  Files          1506       1626        +120     
  Lines        431172     603945     +172773     
=================================================
+ Hits         312580     337815      +25235     
- Misses        99191     242897     +143706     
- Partials      19401      23233       +3832     
Flag Coverage Δ
integration 37.0544% <100.0000%> (?)
unit 71.4326% <0.0000%> (-0.0493%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
dumpling 52.9656% <ø> (ø)
parser ∅ <ø> (∅)
br 50.5410% <ø> (+8.7517%) ⬆️

Copy link

ti-chi-bot bot commented Jun 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, wjhuang2016

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jun 3, 2024
Copy link

ti-chi-bot bot commented Jun 3, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-06-03 08:48:33.508070929 +0000 UTC m=+3284667.265206499: ☑️ agreed by wjhuang2016.
  • 2024-06-03 09:34:51.754440248 +0000 UTC m=+3287445.511575832: ☑️ agreed by lance6716.

@hawkingrei
Copy link
Member

/retest

@lance6716
Copy link
Contributor

FAILED  addindextest4_test.TestAddIndexIngestFailures (2.0s)

@ti-chi-bot ti-chi-bot bot merged commit b23ac8e into pingcap:master Jun 4, 2024
21 checks passed
@Benjamin2037 Benjamin2037 added the needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. label Jul 29, 2024
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-8.1: #55001.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

invalid memory address in the addindex_test
6 participants