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

[cfzjywxk]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

There are some logs and assumptions which are inaccurate or wrong when the async commit protocol is used, they are:

1. https://github.com/pingcap/tidb/blob/master/store/tikv/commit.go#L146 when the async commit protocol is used, the first commit batch which is committed successful may not contain the primary lock, the committed field set logic for async commit transactions needs fixing.
2. The related log https://github.com/pingcap/tidb/blob/master/store/tikv/commit.go#L129 is also needed to update.

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master
release-5.0

[zhaoxugang]

/pick-up

[zhaoxugang]

I'm instrest about transaction,can i try to resolve this issue？@cfzjywxk

[cfzjywxk]

I'm instrest about transaction,can i try to resolve this issue？@cfzjywxk

Sure, you could check about https://github.com/tikv/sig-transaction for more information.