txn: fix some logs and assumptions are inaccurate when the async commit protocol is used

[zhaoxugang]

What problem does this PR solve?

Issue Number: close #23542

Problem Summary:

What is changed and how it works?

Proposal: xxx

What's Changed:

How it Works:

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• Need to cherry-pick to the release branch

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression
  • Consumes more CPU
  • Consumes more MEM
• Breaking backward compatibility

Release note

• fix some logs and assumptions are inaccurate when the async commit protocol is used

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[ti-srebot]

No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md

[zhaoxugang]

PTAL @cfzjywxk

[cfzjywxk]

We may need to mark this field correctly when async commit protocol is used, as the cilent will receive OK packet when all prewrite requests are successfully processed. Then we may need to adjust the error log messages in L129, the debug log in L137 seems ok.

[zhaoxugang]

We may need to mark this field correctly when async commit protocol is used, as the cilent will receive OK packet when all prewrite requests are successfully processed. Then we may need to adjust the error log messages in L129, the debug log in L137 seems ok.

I think the twoPhaseCommitter.mu.commited is true means the primary of batchs was commited,so L129 is ok,but in async commit ,the batch mabe not primary，so L137 mabe not accurate

[sticnarf]

I think we'd better maintain committed for async commit transactions (setting it in 2pc.go after prewriting finishes).
If we maintain `committed for async commit transactions, then "2PC failed commit key after primary key committed" would be inaccurate.

[zhaoxugang]

done

[ti-chi-bot]

@zhaoxugang: 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/test-infra repository.