cpu_cores_quota cause TiKV Panic #12479
Description
Bug Report
What version of TiKV are you using?
master 27bfe30
What operating system and CPU are you using?
CentOS 7.6; running in k8s, container runtime is docker.
Steps to reproduce
What did you expect?
no panic
What did happened?
kubectl logs t1-tikv-0 -n csn
starting tikv-server ...
/tikv-server --pd=http://t1-pd:2379 --advertise-addr=t1-tikv-0.t1-tikv-peer.csn.svc:20160 --addr=0.0.0.0:20160 --status-addr=0.0.0.0:20180 --data-dir=/var/lib/tikv --capacity=200GB --config=/etc/tikv/tikv.toml
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', components/tikv_util/src/sys/cgroup.rs:263:44
stack backtrace:
0: rust_begin_unwind
at ./rustc/1e12aef3fab243407f9d71ba9956cb2a1bf105d5/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at ./rustc/1e12aef3fab243407f9d71ba9956cb2a1bf105d5/library/core/src/panicking.rs:143:14
2: core::panicking::panic
at ./rustc/1e12aef3fab243407f9d71ba9956cb2a1bf105d5/library/core/src/panicking.rs:48:5
3: tikv_util::sys::cgroup::build_path
4: tikv_util::sys::cgroup::CGroupSys::cpuset_cores
5: tikv_util::sys::SysQuota::cpu_cores_quota
6: <tikv::config::TiKvConfig as core::default::Default>::default
7: <tikv::config::_IMPL_DESERIALIZE_FOR_TiKvConfig::<impl serde::de::Deserialize for tikv::config::TiKvConfig>::deserialize::__Visitor as serde::de::Visitor>::visit_map
8: tikv::config::TiKvConfig::from_file
9: tikv_server::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.