In-memory Engine: enable HybridEngine only for storage and coprocessor modules
overvenus opened this issue · comments
Background:
HybridEngine wraps RocksDB and region_cache_memory_engine, providing a unified interface through the engine_traits. Currently, to enable the in-memory engine feature, TiKV has to replace RocksDB with HybridEngine for all components, which could cause compatibility issues.
Problem:
Replacing RocksDB with HybridEngine for all components can lead to potential compatibility problems and increases the testing burden.
Proposal:
Since Storage and Coprocessor are the only components serving write and read requests, we should only enable HybridEngine for these components. This approach will reduce compatibility testing burdens for unrelated components.