Eliaaazzz commented on issue #31422: URL: https://github.com/apache/beam/issues/31422#issuecomment-3734107609
Hi @Arunodoy18, is there any update on PR #36877? I noticed this issue has been open for a while. I've been analyzing the stack trace and the previous attempts by @liferoad (e.g., #35576). It seems that using `synchronized` blocks previously caused performance regressions due to the high contention on `APPEND_CLIENTS` during streaming. Given that `write()` operations heavily outnumber `close()` operations, have we considered using StampedLock (Java 8+) here? Its optimistic read mode could potentially solve the `IllegalStateException` race condition without the overhead of a full `ReentrantReadWriteLock` or `synchronized` block. If the current PR is stalled, I would be interested in prototyping a solution using StampedLock or a segmented locking strategy. -- 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]
