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

session: make TxnInfo() return even if process info is empty (#57044) #57161

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #57044

What problem does this PR solve?

Issue Number: close #57043

Problem Summary:

tidb/pkg/session/session.go

Lines 4026 to 4030 in c240fdf

txnInfo := tmp.TxnInfo()
if txnInfo != nil {
startTS = txnInfo.StartTS
processInfoID = txnInfo.ConnectionID
}

TxnInfo() could be nil if process info is not set(see the implementation of TxnInfo()). Such sessions are commonly used in DDL/DXF:

sessCtx, err := w.sessPool.Get()
if err != nil {
logutil.Logger(w.ctx).Error("tableScanWorker get session from pool failed", zap.Error(err))
w.ctx.onError(err)
return
}
w.se = session.NewSession(sessCtx)

And they only invoke session.Begin() before using:

func wrapInBeginRollback(se *sess.Session, f func(startTS uint64) error) error {
err := se.Begin(context.Background())
if err != nil {
return errors.Trace(err)
}
defer se.Rollback()

As a result, the startTS from internal DDL sessions will not be reported to etcd, and GC safepoint will be advanced unexpectedly.

What changed and how does it work?

Make TxnInfo() return even if process info is empty.

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 added release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. labels Nov 6, 2024
Copy link

codecov bot commented Nov 6, 2024

Codecov Report

Attention: Patch coverage is 89.79592% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@62a1bb5). Learn more about missing BASE report.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-8.5     #57161   +/-   ##
================================================
  Coverage               ?   56.6721%           
================================================
  Files                  ?       1780           
  Lines                  ?     643242           
  Branches               ?          0           
================================================
  Hits                   ?     364539           
  Misses                 ?     254354           
  Partials               ?      24349           
Flag Coverage Δ
integration 36.8057% <51.0204%> (?)
unit 72.5264% <89.7959%> (?)

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

Components Coverage Δ
dumpling 52.9478% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 52.3998% <0.0000%> (?)

Copy link

ti-chi-bot bot commented Nov 12, 2024

PR needs rebase.

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 the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 12, 2024
Copy link
Collaborator

@Benjamin2037 Benjamin2037 left a comment

Choose a reason for hiding this comment

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

LGTM

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Nov 25, 2024
Copy link

ti-chi-bot bot commented Dec 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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 approved lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 2, 2024
Copy link

ti-chi-bot bot commented Dec 2, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-11-25 12:57:42.056451277 +0000 UTC m=+468449.676105790: ☑️ agreed by Benjamin2037.
  • 2024-12-02 04:31:25.286806257 +0000 UTC m=+1042872.906460772: ☑️ agreed by lance6716.

Signed-off-by: lance6716 <[email protected]>
@lance6716
Copy link
Contributor

/retest

@lance6716 lance6716 removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 2, 2024
@ti-chi-bot ti-chi-bot bot added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Dec 2, 2024
@ti-chi-bot ti-chi-bot bot merged commit 0e8ccbc into pingcap:release-8.5 Dec 2, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants