集群扩容tiflash，numa绑核不成功，同样的配置tikv是可以的why?

🪐 TiDB 技术问题
1

【 TiDB 使用环境】生产环境 /测试/ Poc
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题
【遇到的问题：问题现象及影响】
刚刚扩容（新加）了2个节点 tiflash。 发现numa_node 绑核没有成功，同样的配置同一批机器，tikv节点是成功了的。日志也没过滤到有用信息，不知道怎么排查问题大佬们帮忙看看~~
【资源配置】
【附件：截图/日志/监控】

image
image875×364 9.56 KB

image
image1037×416 12.1 KB 

$ tiup cluster show-config tidb-xxxxxxx
tiup is checking updates for component cluster ...
Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.12.1/tiup-cluster show-config tidb-xxxxxxx
global:
  user: tidb
  ssh_port: 17717
  ssh_type: builtin
  deploy_dir: /home/tidb/deploy
  data_dir: /disk2
  os: linux
monitored:
  node_exporter_port: 9100
  blackbox_exporter_port: 9115
  deploy_dir: /home/tidb/deploy/monitor-9100
  data_dir: /disk2/monitor-9100
  log_dir: /home/tidb/deploy/monitor-9100/log
server_configs:
  tidb:
    binlog.enable: false
    binlog.ignore-error: false
    log.slow-threshold: 3000
    mem-quota-query: 3221225472
    proxy-protocol.networks: 192.168.241.54,192.168.241.55,192.168.241.101,192.168.241.100
  tikv:
    readpool.coprocessor.use-unified-pool: true
    readpool.storage.use-unified-pool: false
    rocksdb.defaultcf.block-cache-size: 32GB
    rocksdb.lockcf.block-cache-size: 2.56GB
    rocksdb.writecf.block-cache-size: 19.2GB
  pd:
    replication.enable-placement-rules: true
    schedule.leader-schedule-limit: 4
    schedule.region-schedule-limit: 2048
    schedule.replica-schedule-limit: 64
  tidb_dashboard: {}
  tiflash: {}
  tiflash-learner: {}
  pump: {}
  drainer: {}
  cdc: {}
  kvcdc: {}
  grafana: {}

tikv_servers:
- host: 192.168.241.73
  ssh_port: 17717
  port: 20160
  status_port: 20180
  deploy_dir: /home/tidb/deploy/tikv-20160
  data_dir: /disk2/tikv-20160
  log_dir: /home/tidb/deploy/tikv-20160/log
  numa_node: "1"
  arch: amd64
  os: linux
- host: 192.168.241.74
  ssh_port: 17717
  port: 20160
  status_port: 20180
  deploy_dir: /home/tidb/deploy/tikv-20160
  data_dir: /disk2/tikv-20160
  log_dir: /home/tidb/deploy/tikv-20160/log
  numa_node: "1"
  arch: amd64
  os: linux
- host: 192.168.241.75
  ssh_port: 17717
  port: 20160
  status_port: 20180
  deploy_dir: /home/tidb/deploy/tikv-20160
  data_dir: /disk2/tikv-20160
  log_dir: /home/tidb/deploy/tikv-20160/log
  numa_node: "1"
  arch: amd64
  os: linux
- host: 192.168.241.76
  ssh_port: 17717
  port: 20160
  status_port: 20180
  deploy_dir: /home/tidb/deploy/tikv-20160
  data_dir: /disk2/tikv-20160
  log_dir: /home/tidb/deploy/tikv-20160/log
  numa_node: "1"
  arch: amd64
  os: linux
tiflash_servers:
- host: 192.168.241.71
  ssh_port: 17717
  tcp_port: 9000
  http_port: 8123
  flash_service_port: 3930
  flash_proxy_port: 20170
  flash_proxy_status_port: 20292
  metrics_port: 8234
  deploy_dir: /home/tidb/deploy/tiflash-9000
  data_dir: /disk2/tiflash-9000
  log_dir: /home/tidb/deploy/tiflash-9000/log
  numa_node: "1"
  arch: amd64
  os: linux
- host: 192.168.241.72
  ssh_port: 17717
  tcp_port: 9000
  http_port: 8123
  flash_service_port: 3930
  flash_proxy_port: 20170
  flash_proxy_status_port: 20292
  metrics_port: 8234
  deploy_dir: /home/tidb/deploy/tiflash-9000
  data_dir: /disk2/tiflash-9000
  log_dir: /home/tidb/deploy/tiflash-9000/log
  numa_node: "1"
  arch: amd64
  os: linux
2

lscpu 看看node 信息

3

是同一批机器，硬件完全相同，tikv的节点绑核是成功的

# lscpu 
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                48
On-line CPU(s) list:   0-47
Thread(s) per core:    2
Core(s) per socket:    12
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 106
Model name:            Intel(R) Xeon(R) Silver 4310 CPU @ 2.10GHz
Stepping:              6
CPU MHz:               3300.476
CPU max MHz:           3300.0000
CPU min MHz:           800.0000
BogoMIPS:              4200.00
Virtualization:        VT-x
L1d cache:             48K
L1i cache:             32K
L2 cache:              1280K
L3 cache:              18432K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 invpcid_single intel_pt ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq md_clear pconfig spec_ctrl intel_stibp flush_l1d arch_capabilities
4

直接tiup cluster edit-config clustername修改一下配置将tiflash_servers中192.168.241.71的 numa_node: "1"改成 numa_node: "0"啊。我看你tikv也绑定的都是1啊

5

为啥要改成绑 0啊？ 我这是6个不同的机器， 4个tikv ，2个tiflash，没有占用

6

没细看，那你没有混合部署的话为啥要绑核啊？你现在都绑的1不是对的吗？

7

你可以把tiflash的绑定设置为：numa_node: “0” ，然后reload 一下tiflash试试，没有错误日志，只能通过切换一下参数，试试有没有变化

8

是要绑1，要和其他的服务混。。。

9

好的，我试下~

10

要绑1的话，你不是已经绑上了？

11

没有啊，你看截图1，没有绑定成功，tikv是成功的

12

尝试了下，不行， 日志好像也不会打印相关的信息吧？ 我过滤的numa关键字，直接没有内容
find log/ -type f |xargs grep -i ‘numa’

13

但是我看你show config已经绑过了啊？

14

这个只是有这个配置而己，实际没有生效看截图

15

reload过集群了？

16

看着是配置没下发啊，reload下 tiflash

17

restart 过tiflash，
也修改过numa_node： 0/1 ，reload过，没用

18

不应该啊，tiflash和tikv绑核没啥不一样的啊

19

对啊，配置一样，服务器都是同一批机器硬件系统都相同

20

刚刚缩容这俩节点，重新扩容TIFLASH，还是一样的效果～～～～
下面怎么排查呀，没思路了～～