dybyte commented on issue #9817: URL: https://github.com/apache/seatunnel/issues/9817#issuecomment-3256967783
> 不过任务卡顿定位到了一个可能性比较大的原因，咱们在TaskExecutionService.updateMetricsContextInImap、JobMaster.removeMetricsContext时在之前的版本用的Imap.tryLock这种方式、 The approach you described, using an async queue and a separate thread for metrics updates, is interesting. However, it could potentially introduce thread-safety issues, which may result in inconsistent or incorrect metrics being displayed. If switching from distributed locks to synchronized still does not address the performance bottleneck, another option might be to revisit the single-key design of metricsImap. By partitioning the metrics into multiple keys and managing them separately, we could reduce contention. @Hisoka-X What do you think about exploring this direction? -- 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]
