Skip to content

disagg: Add exclusive label for tiflash compute node (release-8.1)#9893

Merged
ti-chi-bot[bot] merged 2 commits intopingcap:release-8.1from
JaySon-Huang:add_cn_exclusive_81
Feb 20, 2025
Merged

disagg: Add exclusive label for tiflash compute node (release-8.1)#9893
ti-chi-bot[bot] merged 2 commits intopingcap:release-8.1from
JaySon-Huang:add_cn_exclusive_81

Conversation

@JaySon-Huang
Copy link
Contributor

cherry-pick of #9849

What problem does this PR solve?

Issue Number: close #9750

Problem Summary:

When creating a placement policy through tidb, tidb will create a placement-rule with "engine" notIn "tiflash" pingcap/tidb#22065
However, under tiflash disaggregated compute and storage arch, the compute node will register store with label {"engine": "tiflash_compute"}.

The logic in PD of choosing store for rule: pkg/schedule/placement/label_constraint.go @ pd

  1. If the store's label.key is equal to "engine" (or "exclusive," or starts with '$'), and the rule's constraint does not contain a rule with the same label.key, then do not schedule the peer to this store.
  2. Otherwise, further check if the rule's constraint matches the store's label. If it matches, schedule the peer to this store.

So the PD would pick tiflash compute node as target store to place the Region peer.

What is changed and how it works?

Add a label with {"exclusive": "no-data"}, so that PD won't select TiFlash compute node stores for placing Region

We avoid Region data being placed to TiFlash compute node in 2 ways:

Check List

Tests

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

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Fix a bug that after executing `ALTER TABLE ... PLACEMENT POLICY ...` Region peers may be unexpectedly added to the TiFlash Compute Node in the disaggregated storage and compute architecture

close pingcap#9750

Add a label with {"exclusive": "no-data"}, so that PD won't select TiFlash compute node stores for placing Region

Signed-off-by: JaySon-Huang <tshent@qq.com>
@ti-chi-bot ti-chi-bot bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved cherry-pick-approved Cherry pick PR approved by release team. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed do-not-merge/cherry-pick-not-approved labels Feb 19, 2025
@ti-chi-bot ti-chi-bot bot added needs-1-more-lgtm Indicates a PR needs 1 more LGTM. approved labels Feb 19, 2025
Copy link
Member

@CalvinNeo CalvinNeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Signed-off-by: JaySon-Huang <tshent@qq.com>
@ti-chi-bot ti-chi-bot bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 19, 2025
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JinheLin, Lloyd-Pottiger

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:
  • OWNERS [JinheLin,Lloyd-Pottiger]

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 lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Feb 20, 2025
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Feb 20, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-02-19 07:15:56.516741563 +0000 UTC m=+1031998.912963625: ☑️ agreed by JinheLin.
  • 2025-02-20 01:51:01.415977753 +0000 UTC m=+1098903.812199816: ☑️ agreed by Lloyd-Pottiger.

@ti-chi-bot ti-chi-bot bot merged commit 726f4c0 into pingcap:release-8.1 Feb 20, 2025
4 checks passed
@JaySon-Huang JaySon-Huang deleted the add_cn_exclusive_81 branch February 20, 2025 02:04
JaySon-Huang added a commit to JaySon-Huang/tiflash that referenced this pull request Apr 25, 2025
…ingcap#9893)

close pingcap#9750

Add a label with {"exclusive": "no-data"}, so that PD won't select TiFlash compute node stores for placing Region

Signed-off-by: JaySon-Huang <tshent@qq.com>
JaySon-Huang added a commit that referenced this pull request Apr 25, 2025
…#10134)

Note:
* This change to the FFI interface for proxy adaptation. And the related
issue is currently suspected to potentially cause fluctuations in
LearnerRead latency in some cases.
#9841,
#9882
* This change to the FFI interface for proxy adaptation
#9893
* Fix stale read can not eliminate the learner read
#10132


### What problem does this PR solve?

Issue Number: ref #4982, close
#10046

Problem Summary:
 update proxy to raftstore-proxy-8.1
 Proxy PR: 
 Including:\nSubmodule contrib/tiflash-proxy caa7a0c1dd..96545a2632:
  > Fix safe ts not updated (#429) (#434)

The leader_safe_ts, self_safe_ts are always 0 in the TiFlash side,
making TiFlash can not eliminate the learner read on region without any
updates.

### What is changed and how it works?

For detailed reasons why safe_ts failed to be updated, checkout the
description on pingcap/tidb-engine-ext#429.

### Check List

Tests <!-- At least one of them must be included. -->

- [ ] Unit test
- [ ] Integration test
- [x] Manual test (add detailed scripts or steps below)
- [ ] No code

Side effects

- [ ] Performance regression: Consumes more CPU
- [ ] Performance regression: Consumes more Memory
- [ ] Breaking backward compatibility

Documentation

- [ ] Affects user behaviors
- [ ] Contains syntax changes
- [ ] Contains variable changes
- [ ] Contains experimental features
- [ ] Changes MySQL compatibility

### Release note

<!-- bugfix or new feature needs a release note -->

```release-note
Fix the issue that `SELECT ... AS OF TIMESTAMP` can not eliminate the learner read on TiFlash as expected
```

---------

Signed-off-by: Calvin Neo <calvinneo1995@gmail.com>
Signed-off-by: JaySon-Huang <tshent@qq.com>
Signed-off-by: CalvinNeo <calvinneo1995@gmail.com>
Co-authored-by: Calvin Neo <CalvinNeo@users.noreply.github.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Co-authored-by: Calvin Neo <calvinneo1995@gmail.com>
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. lgtm release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants