pingcap / pingcap/tiflash

the tiflash of the tiup playground cluster will quite in a few minutes

Open
#5,337 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/storage severity/moderate type/bug
Dominant language
C++
Stars
1k
Forks
423
Avg merge
1d 15h
Merged PRs (30d)
24

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)
  1. tiup playground nightly on macos
➜  ~ uname -a
Darwin aytrackMBP.local 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64  /0.0s

2. What did you expect to see? (Required)

tiflash start successfully and not quite

3. What did you see instead (Required)

tiflash will quite in a few minutes.

CLUSTER START SUCCESSFULLY, Enjoy it ^-^
To connect TiDB: mysql --comments --host 127.0.0.1 --port 4000 -u root -p (no password)
To view the dashboard: http://127.0.0.1:2379/dashboard
PD client endpoints: [127.0.0.1:2379]
To view the Prometheus: http://127.0.0.1:9090
To view the Grafana: http://127.0.0.1:3000
tiflash quit: signal: illegal instruction
Logging debug to /Users/aytrack/.tiup/data/TBG65L1/tiflash-0/log/tiflash.log
Logging errors to /Users/aytrack/.tiup/data/TBG65L1/tiflash-0/log/tiflash_error.log
deprecated configuration, log-file has been moved to log.file.filename
override log.file.filename with log-file, "/Users/aytrack/.tiup/data/TBG65L1/tiflash-0/log/tiflash_tikv.log"
...
check detail log from: /Users/aytrack/.tiup/data/TBG65L1/tiflash-0/tiflash.log

the log

[2022/07/11 14:50:26.721 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.89% of capacity size. Avail size: 78.66 GiB, used size: 1.00 B, capacity size: 465.63 GiB"] [thread_id=8]
[2022/07/11 14:50:36.724 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.90% of capacity size. Avail size: 78.67 GiB, used size: 4.99 KiB, capacity size: 465.63 GiB"] [thread_id=8]
[2022/07/11 14:50:46.726 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.90% of capacity size. Avail size: 78.67 GiB, used size: 4.99 KiB, capacity size: 465.63 GiB"] [thread_id=8]
[2022/07/11 14:50:56.728 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.90% of capacity size. Avail size: 78.67 GiB, used size: 4.99 KiB, capacity size: 465.63 GiB"] [thread_id=8]
[2022/07/11 14:51:06.730 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.90% of capacity size. Avail size: 78.67 GiB, used size: 4.99 KiB, capacity size: 465.63 GiB"] [thread_id=8]
[2022/07/11 14:51:08.183 +08:00] [ERROR] [BaseDaemon.cpp:377] [BaseDaemon:########################################] [thread_id=13]
[2022/07/11 14:51:08.183 +08:00] [ERROR] [BaseDaemon.cpp:378] ["BaseDaemon:(from thread 12) Received signal Illegal instruction: 4(4)."] [thread_id=13]
[2022/07/11 14:51:08.183 +08:00] [ERROR] [BaseDaemon.cpp:470] ["BaseDaemon:Illegal opcode."] [thread_id=13]
[2022/07/11 14:51:08.188 +08:00] [ERROR] [BaseDaemon.cpp:570] ["BaseDaemon:\n  0x7ff801498ee3\t__os_unfair_lock_recursive_abort [libsystem_platform.dylib+140703132020451]"] [thread_id=13]
[2022/07/11 14:51:16.735 +08:00] [WARN] [PathCapacityMetrics.cpp:196] ["PathCapacityMetrics:Available space is only 16.90% of capacity size. Avail size: 78.67 GiB, used size: 4.99 KiB, capacity size: 465.63 GiB"] [thread_id=8]
4. What is your TiFlash version? (Required)
Start tiflash instance:v6.2.0-alpha-nightly-20220710

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with tiup playground nightly on macOS and inspect the reported tiflash.log and tiflash_error.log paths under the TiUP data directory. Start with the Illegal instruction and __os_unfair_lock_recursive_abort entries in the logs, then determine why the TiFlash instance exits after starting. Done means the nightly playground TiFlash instance remains running on the reported macOS environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
databases, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.