Dear Apache Fluss Community Developers, I’m a R&D engineer from Xiaomi. We’re currently testing *Apache Fluss 0.9.1* for our internal business scenarios, and ran into several severe unstable issues during our tests. I’d like to share these problems and ask for your guidance.
Here are the some main issues we encountered: *1. RPC stuck issue*: RPC requests (e.g. update metadata request) from Coordinator Server to Tablet Server often get stuck for a long time, causing service blocking. *2. Partition not exist error*: Data writing throws partition-not-exist exceptions even when the target partitions exist normally. *3. RocksDB lock blocking issue*: After abnormal restart of Tablet Server nodes, a lot of KV buckets leader switching occurs. The RocksDB open process holds locks for a long time, seriously blocking other worker threads. I'm not sure whether these problems are caused by our improper usage, configuration mistakes, or existing known bugs of Fluss 0.9.1. And I’d like to consult the community whether Fluss 0.9.1 currently is recommended for production environment deployment? We really want to adopt Fluss in our business environment. Thanks a lot for your help! Looking forward to your reply. Best regards, Zuo Wei Email: [email protected]
