Failed to Deploy TiFlash in TiDB 6.5.0

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb 6.5.0部署tiflash失败

| username: devopNeverStop

[TiDB Usage Environment] Production Environment / Testing / Poc
Production Environment
[TiDB Version]
v6.5.0
[Reproduction Path] What operations were performed when the issue occurred
Deployed v6.5.0 but TiFlash failed to start. After removing the TiFlash content from the topology and redeploying, it succeeded. However, deploying TiFlash again via scale-out still failed to start TiFlash normally.
[Encountered Issue: Issue Phenomenon and Impact]
TiFlash failed to start, status is N/A
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
Mar 01 17:36:31 tiflash01 systemd[1]: tiflash-9000.service holdoff time over, scheduling restart.
Mar 01 17:36:31 tiflash01 systemd[1]: Stopped tiflash service.
– Subject: Unit tiflash-9000.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit tiflash-9000.service has finished shutting down.
Mar 01 17:36:31 tiflash01 systemd[1]: Started tiflash service.
– Subject: Unit tiflash-9000.service has finished start-up
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit tiflash-9000.service has finished starting up.

– The start-up result is done.
Mar 01 17:36:31 tiflash01 bash[12684]: sync …
Mar 01 17:36:31 tiflash01 bash[12684]: real 0m0.015s
Mar 01 17:36:31 tiflash01 bash[12684]: user 0m0.000s
Mar 01 17:36:31 tiflash01 bash[12684]: sys 0m0.002s
Mar 01 17:36:31 tiflash01 bash[12684]: ok
Mar 01 17:36:31 tiflash01 systemd[1]: tiflash-9000.service: main process exited, code=dumped, status=4/ILL
Mar 01 17:36:31 tiflash01 systemd[1]: Unit tiflash-9000.service entered failed state.
Mar 01 17:36:31 tiflash01 systemd[1]: tiflash-9000.service failed.

| username: 我是咖啡哥 | Original post link

Check the logs of the TiFlash node.

| username: devopNeverStop | Original post link

Empty, no logs.

| username: tidb菜鸟一只 | Original post link

Is TiFlash deployed on a separate machine?

| username: devopNeverStop | Original post link

Yes.

| username: 我是咖啡哥 | Original post link

How about directly going to the TiFlash node and starting it with a script?

| username: devopNeverStop | Original post link

Image

| username: 裤衩儿飞上天 | Original post link

See if it supports the AVX2 instruction set.

| username: devopNeverStop | Original post link

No

| username: 裤衩儿飞上天 | Original post link

The image is not visible. Please provide the text you need translated.

| username: 裤衩儿飞上天 | Original post link

It should be from version 6.3.
Reference: TiDB 6.3.0 Release Notes | PingCAP Documentation Center

| username: 我是咖啡哥 | Original post link

When upgrading TiFlash from versions prior to v6.3.0 to v6.3.0 and later, please pay special attention: When deploying TiFlash on hardware platforms with the Linux AMD64 architecture, the CPU must support the AVX2 instruction set. When deploying TiFlash on hardware platforms with the Linux ARM64 architecture, the CPU must support the ARMv8 architecture. For details, please refer to the description in the 6.3.0 version Release Notes.

Here is the explanation.

| username: devopNeverStop | Original post link

Can only use the lower version of TiFlash??!!

| username: solotzg-PingCAP | Original post link

Are you using a virtualization platform or a physical environment? The AVX2 instruction set was released around 2011, and mainstream cloud providers’ environments already support it by default. For virtual machines, it is recommended to configure the CPU architecture as Haswell.

| username: devopNeverStop | Original post link

Okay, I will take a look, thank you.

| username: devopNeverStop | Original post link

The virtual machine’s AVX2 is enabled, and TiFlash is finally up and running. Thanks to all the TiDB friends for their help!

| username: devopNeverStop | Original post link

There is a minor issue: when running tiup cluster display --uptime, the TiFlash component does not show the “since” time. Even after scaling in and then scaling out TiFlash, the issue remains the same.
Image

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.