loserwang1024 opened a new issue, #3362: URL: https://github.com/apache/fluss/issues/3362
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### 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? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
