-
Notifications
You must be signed in to change notification settings - Fork 411
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
Number of physical core detected by tiflash compute node(Disagg Mode) is not accurate #7436
Labels
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
Use this command:
So the number of physical cores collected by proxy is correct. So we need to copy proxy code for CN.( Because CN doesn't start proxy). |
guo-shaoge
changed the title
Number of physical core in tiflash compute node is wrong
Number of physical core detected by tiflash compute node is not accurate
May 8, 2023
This was referenced May 31, 2023
guo-shaoge
changed the title
Number of physical core detected by tiflash compute node is not accurate
Number of physical core detected by tiflash compute node(Disagg Mode) is not accurate
May 31, 2023
guo-shaoge
added
affects-7.1
This bug affects the 7.1.x(LTS) versions.
and removed
may-affects-5.1
may-affects-5.2
may-affects-5.3
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
labels
May 31, 2023
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
Actual cpu info: 8 cores
3. What did you see instead (Required)
TiFlash Compute Node (in Disagg Mode)only see 4 cores
4. What is your TiFlash version? (Required)
master
The text was updated successfully, but these errors were encountered: