Skip to content

Rollup of In-memory Engine commits #17805, #17515, #17771, #17763 and #17747#17831

Merged
ti-chi-bot[bot] merged 5 commits intotikv:release-8.5from
overvenus:ime/release-8.5
Nov 15, 2024
Merged

Rollup of In-memory Engine commits #17805, #17515, #17771, #17763 and #17747#17831
ti-chi-bot[bot] merged 5 commits intotikv:release-8.5from
overvenus:ime/release-8.5

Conversation

@overvenus
Copy link
Member

What is changed and how it works?

Issue Number:

ref #17767
ref #16141

What's Changed:

In-memory engine: handle error when getting regions info (#17805)

ref tikv/tikv#16141

handle error when getting regions info

Signed-off-by: SpadeA-Tang <u6748471@anu.edu.au>

---

In-memory Engine: Adjust memory settings based on available memory (#17515)

ref tikv/tikv#16141

This commit adjusts the following in-memory-engine defaults:

* `capacity`: Now IME uses 10% of the block cache and takes an equal
  amount of memory from the system. This is based on tests showing that
  the IME rarely fills its full capacity.
* `mvcc_amplification_threshold`: Change from 100 to 10 which benefit
  common workloads like TPCc (50 warehouse), saving approximately 20%
  of unified read pool CPU usage.

Also, it addresses two security issues:

* Upgrade hashbrown from yanked 0.15.0 to 0.15.1

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory Engine: fix panic when destroy an uninitialized region (#17771)

close tikv/tikv#17767

IME observes all peer destroy events to timely evict regions. By adding
a new peer, the old and uninitialized peer will be destroyed and IME
must not panic in this situation.

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory Engine: remove dead code and fix typos (#17763)

ref tikv/tikv#16141

Signed-off-by: Neil Shen <overvenus@gmail.com>

---

In-memory engine: use stop-load-threshold for loading new regions (#17747)

ref tikv/tikv#16141

use stop-load-threshold for loading new regions

Signed-off-by: SpadeA-Tang <tangchenjie1210@gmail.com>

Check List

Tests

  • Unit test
  • Integration test

Release note

None

@overvenus overvenus added the type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. label Nov 15, 2024
@ti-chi-bot ti-chi-bot bot added the cherry-pick-approved Cherry pick PR approved by release team. label Nov 15, 2024
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 15, 2024

@overvenus: You cannot manually add or delete the cherry pick branch category labels. It will be added automatically by bot when the PR is created.

Details

In response to adding label named type/cherry-pick-for-release-8.5.

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 ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot bot removed the type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. label Nov 15, 2024
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the dco. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 15, 2024
SpadeA-Tang and others added 5 commits November 15, 2024 14:26
…kv#17747)

ref tikv#16141

use stop-load-threshold for loading new regions

Signed-off-by: SpadeA-Tang <tangchenjie1210@gmail.com>
Signed-off-by: Neil Shen <overvenus@gmail.com>
ref tikv#16141

Signed-off-by: Neil Shen <overvenus@gmail.com>
…v#17771)

close tikv#17767

IME observes all peer destroy events to timely evict regions. By adding
a new peer, the old and uninitialized peer will be destroyed and IME
must not panic in this situation.

Signed-off-by: Neil Shen <overvenus@gmail.com>
…ikv#17515)

ref tikv#16141

This commit adjusts the following in-memory-engine defaults:

* `capacity`: Now IME uses 10% of the block cache and takes an equal
  amount of memory from the system. This is based on tests showing that
  the IME rarely fills its full capacity.
* `mvcc_amplification_threshold`: Change from 100 to 10 which benefit
  common workloads like TPCc (50 warehouse), saving approximately 20%
  of unified read pool CPU usage.

Also, it addresses two security issues:

* Upgrade hashbrown from yanked 0.15.0 to 0.15.1

Signed-off-by: Neil Shen <overvenus@gmail.com>
ref tikv#16141

handle error when getting regions info

Signed-off-by: SpadeA-Tang <u6748471@anu.edu.au>
Signed-off-by: Neil Shen <overvenus@gmail.com>
@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 15, 2024
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 15, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-11-15 06:17:57.106952721 +0000 UTC m=+596239.297821718: ☑️ agreed by glorv.
  • 2024-11-15 06:28:56.20033409 +0000 UTC m=+596898.391203087: ☑️ agreed by SpadeA-Tang.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, glorv, SpadeA-Tang

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

The pull request process is described here

Details 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 the approved label Nov 15, 2024
@ti-chi-bot ti-chi-bot bot merged commit b7b0cd9 into tikv:release-8.5 Nov 15, 2024
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. dco-signoff: yes Indicates the PR's author has signed the dco. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants