pingcap / pingcap/tiflash

tiflash deploy error

Open
#7,784 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/storage may-affects-5.4 may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major type/bug
Dominant language
C++
Stars
1k
Forks
423
Avg merge
1d 15h
Merged PRs (30d)
24

Description

1. Minimal reproduce step

use tiup deplaoy 7.1 lts, tiflash not able to start.

2. What did you expect to see?

expect the service work

3. What did you see instead (Required)

check the logs, this is the last error:

[2023/07/10 13:54:46.512 +00:00] [INFO] [engine.rs:80] ["disabled pagestorage"]
[2023/07/10 13:54:49.775 +00:00] [FATAL] [lib.rs:497] ["called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: \"Resource temporarily unavailable\" }"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/boxed.rs:2032:9\n      std::panicking::rust_panic_with_hook\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:692:13\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:579:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/sys_common/backtrace.rs:137:18\n   4: rust_begin_unwind\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:575:5\n   5: core::panicking::panic_fmt\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/core/src/panicking.rs:65:14\n   6: core::result::unwrap_failed\n             at /rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/core/src/result.rs:1791:5\n   7: tikv::read_pool::build_yatp_read_pool\n   8: proxy_server::run::TiKvServer<ER>::init_servers\n   9: proxy_server::run::run_tikv_proxy\n  10: proxy_server::proxy::run_proxy\n  11: _ZN2DB20RaftStoreProxyRunner20runRaftStoreProxyFFIEPv\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tics/dbms/src/Server/Server.cpp:519:9\n  12: start_thread\n  13: __clone3\n"] [location=/root/.cargo/git/checkouts/yatp-e704b73c3ee279b6/5523a9a/src/pool/builder.rs:116] [thread_name=<unnamed>]
4. What is your TiFlash version? (Required)

tiflash-v7.1.0-linux-amd64.tar.gz

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 the TiFlash v7.1.0 deployment with tiup and start from the fatal stack trace in engine.rs, lib.rs, and yatp's builder.rs:116. Trace the call through proxy_server and the TiKV server entry in dbms/src/Server/Server.cpp, then verify the service starts without the Resource temporarily unavailable panic.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.