zengqingfu1442

> Need following information to continue investigating. > > ``` > kubectl get leases -n harvester-system -oyaml > > kubectl logs -n cattle-provisioning-capi-system capi-controller-manager-79ddf9b9d8-vhk99 > #if pod name is wrong,...

Does the harvester need at least two NICs on this machine?

Any workaround? I also came across this issue.

> @zengqingfu1442 Could you submit a PR for this. i have no idea about how to fix this.

Yes, I know. It is supported in RocksDB now and installed it on my machine. But should I rewrite it with rust language?

Thanks, but how can I build the TiKV with the new storage engine RocksDB supporting new compression type ?

Thanks, I see. Should I also put the source code of rocksdb which I have modified in my own rust-rocksdb repository? And put where?

Thanks, I see. Now, i have used tidb-ansible to deploy a TiDB cluster(including TiDB server, PD server and TiKV server), should I install my own RocksDB on each node?

Thanks, but why don't rocksdb for TiKV use JEMALLOC when compiling? https://github.com/pingcap/rust-rocksdb/blob/master/librocksdb_sys/build.sh#L138

Thanks, Jay Lee. Can use the librocksdb_sys/build.sh other than build.rs written in librocksdb_sys/Cargo.toml when compiling rust-rocksdb? @BusyJay