-
Notifications
You must be signed in to change notification settings - Fork 9
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
[deprecated] Adapt to TiKV's raft grpc message filter #413
Conversation
close tikv#16818 Fix duplicated keys returned scanning locks. Signed-off-by: cfzjywxk <cfzjywxk@gmail.com>
…ikv#18095) close tikv#18117 Introduce a new field `use_one_pc` to the `Lock` struct to indicate whether the txn uses 1pc, and use it to prevent locks from being skipped when reading with max-ts. Signed-off-by: zyguan <zhongyangguan@gmail.com>
…8099) ref tikv#15990 * Increase task wait metrics upper limit from 2.5s to 42s to capture long task wait records that are crucial for investigating high latency issues * Add description for end-point-memory-quota configuration Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ref tikv#14474 Fix the request source check logic for external or internal Signed-off-by: cfzjywxk <cfzjywxk@gmail.com>
…ikv#18102) close tikv#17995 Address clock-skew issues. Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
close tikv#18125 Fix incorrect mapped allocation per thread metric Not all thread builders are hooked by `thread_allocate_exclusive_arena`, so some threads are using shared arena, causing incorrect per thread allocation. Signed-off-by: Connor1996 <zbk602423539@gmail.com>
close tikv#18111 Support scalar function from_unixtime in tikv Signed-off-by: wshwsh12 <793703860@qq.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
close tikv#18113 Support customized raft message rejection logic Signed-off-by: Calvin Neo <CalvinNeo@users.noreply.github.com> Signed-off-by: Calvin Neo <calvinneo1995@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com> Co-authored-by: glorv <glorvs@163.com>
Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com> Signed-off-by: ekexium <eke@fastmail.com> Signed-off-by: Calvin Neo <calvinneo1995@gmail.com> Co-authored-by: MyonKeminta <9948422+MyonKeminta@users.noreply.github.com> Co-authored-by: ekexium <eke@fastmail.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
/retest |
/retest |
@CalvinNeo: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Seems that most commits has been merged to raftstore-proxy by #412 . But those commit still present in this PR. This is confusing. Maybe reset the base of your branch to the latest raftstore-proxy and pick the commit you changed? |
It is because the former commit is stashed committed... |
/hold |
What is changed and how it works?
Issue Number: Close #xxx
What's Changed:
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note