doleyzi opened a new issue, #12137: URL: https://github.com/apache/inlong/issues/12137
### What happened <img width="1247" height="505" alt="Image" src="https://github.com/user-attachments/assets/a730b892-1522-4ba0-9051-3a93381c88d7"; /> Under high-concurrency calls, the Audit SDK exhibits several thread-safety issues: - Audit counters (sum / count / size) produce lost or inconsistent updates, leading to incorrect metrics. - Internal aggregation structures intermittently throw ConcurrentModificationException / NullPointerException. - Duplicate or missing audit records are occasionally emitted for the same event. ### What you expected to happen The Audit SDK is embedded in multi-threaded components (Sort / DataProxy / TubeMQ / user apps) and should therefore be thread-safe by contract on all public APIs (add, send, flush, …): - Aggregated counts/sizes per (auditId, logTime) must be exact — no lost or double counting. - No concurrency-related exceptions thrown from SDK internals. - No deadlock, livelock, or unbounded memory growth. - No significant throughput regression vs. single-threaded baseline. ### How to reproduce The probability of this issue occurring is extremely low, making it difficult to reproduce. ### Environment _No response_ ### InLong version 2.3.0 ### InLong Component InLong Audit ### Are you willing to submit PR? - [x] Yes, I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
