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.

Sign up for GitHub

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

Docs special week for troubleshoot-lock-conflicts #3206

Merged
merged 13 commits into from
May 26, 2020
Merged

Docs special week for troubleshoot-lock-conflicts #3206

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
67f558c
troubleshoot-lock-conflicts-pictures
zhenjiaogao May 21, 2020
782f6dc
add file troubleshoot-lock-conflicts
zhenjiaogao May 21, 2020
8ce5738
Update SW troubleshoot-lock-conflicts
zhenjiaogao May 25, 2020
63a91d4
refine format and content
May 25, 2020
a7ee43e
Update SW troubleshoot-lock-conflicts
zhenjiaogao May 26, 2020
f968e11
Update troubleshoot-lock-conflicts.md
zhenjiaogao May 26, 2020
d905dd6
Update SW troubleshoot-lock-conflicts
zhenjiaogao May 26, 2020
bf65193
Update the ci format for troubleshooting lock conflicts
zhenjiaogao May 26, 2020
cb3a65d
refine content
May 26, 2020
782309a
fix indentation
May 26, 2020
ad8fff5
change category
yikeke May 26, 2020
3023cbb
Merge branch 'docs-special-week' into docs-special-week
kissmydb May 26, 2020
8d14291
Merge branch 'docs-special-week' into docs-special-week
kissmydb May 26, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix indentation
  • Loading branch information
yikeke committed May 26, 2020
commit 782309a01707c4f0e20c36b338c4fd950c83a2d0
6 changes: 3 additions & 3 deletions troubleshoot-lock-conflicts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,10 @@ Txn0 完成了 Prewrite，在 Commit 的过程中 Txn1 对该 key 发起了读

* 通过 TiDB Grafana 监控分析：

观察 KV Errors 下 Lock Resolve OPS 面板中的 not_expired/resolve 监控项以及 KV Backoff OPS 面板中的 txnLockFast 监控项，如果有较为明显的上升趋势，那么可能是当前的环境中出现了大量的读写冲突。其中，not_expired 是指对应的锁还没有超时，resolve 是指尝试清锁的操作，txnLockFast 代表出现了读写冲突。
观察 KV Errors 下 Lock Resolve OPS 面板中的 not_expired/resolve 监控项以及 KV Backoff OPS 面板中的 txnLockFast 监控项，如果有较为明显的上升趋势，那么可能是当前的环境中出现了大量的读写冲突。其中，not_expired 是指对应的锁还没有超时，resolve 是指尝试清锁的操作，txnLockFast 代表出现了读写冲突。

![KV-backoff-txnLockFast-optimistic](/media/troubleshooting-lock-pic-09.png)
![KV-Errors-resolve-optimistic](/media/troubleshooting-lock-pic-08.png)
![KV-backoff-txnLockFast-optimistic](/media/troubleshooting-lock-pic-09.png)
![KV-Errors-resolve-optimistic](/media/troubleshooting-lock-pic-08.png)

* 通过 TiDB 日志分析：

Expand Down