Search before asking
Fluss version
0.9.0 (latest release)
Please describe the bug 🐞
Currently, if a partition written job run for a long time, fluss partition info will increase more and more, and never be cleanup. Most of the partition info is no longer used. This will occupy a lot cpu usage for Sender#sendWriteData ->Sender#sendWriteData -> writeBatches.entrySet() and RecordAccumulator#drain - RecordAccumulator#drainBatchesForOneNode -> Cluster#getAvailableBucketsForPhysicalTablePath
Only restart the job, need to clearup:
- useless PhysicalTablePath in org.apache.fluss.client.write.RecordAccumulator#writeBatches
- uneless parittion info in Cluster
Solution
No response
Are you willing to submit a PR?
Search before asking
Fluss version
0.9.0 (latest release)
Please describe the bug 🐞
Currently, if a partition written job run for a long time, fluss partition info will increase more and more, and never be cleanup. Most of the partition info is no longer used. This will occupy a lot cpu usage for
Sender#sendWriteData ->Sender#sendWriteData -> writeBatches.entrySet()andRecordAccumulator#drain - RecordAccumulator#drainBatchesForOneNode -> Cluster#getAvailableBucketsForPhysicalTablePathOnly restart the job, need to clearup:
Solution
No response
Are you willing to submit a PR?