reuvenlax commented on issue #31422: URL: https://github.com/apache/beam/issues/31422#issuecomment-3736924404
Is this issue still occurring? Part of the problem in the past is that the issue was not understood - it's believed that appropriate locking is in place, so clearly there's a bug somewhere. We need to diagnose the issue if it still happens, not simply throw locks into the code without understanding what is being fied. On Sat, Jan 10, 2026 at 10:47 PM Arunodoy Banerjee ***@***.***> wrote: > *Arunodoy18* left a comment (apache/beam#31422) > <https://github.com/apache/beam/issues/31422#issuecomment-3734114281> > .Hi, thanks for the ping. I’m not currently working on this issue or the > PR, so I don’t have an update. Hopefully one of the maintainers can > comment. > > Get Outlook for Android<https://aka.ms/AAb9ysg> > ________________________________ > From: Elia LIU ***@***.***> > Sent: Sunday, January 11, 2026 12:10:13 PM > To: apache/beam ***@***.***> > Cc: Arunodoy Banerjee ***@***.***>; Mention ***@***.***> > Subject: Re: [apache/beam] [Bug]: Issue with IllegalStateException in > `STORAGE_WRITE_API` method in `BigQueryIO` (Issue #31422) > > [https://avatars.githubusercontent.com/u/204549980?s=20&v=4]Eliaaazzz > left a comment (apache/beam#31422)< > https://github.com/apache/beam/issues/31422#issuecomment-3734107609> > > Hi @Arunodoy18<https://github.com/Arunodoy18>, is there any update on PR > #36877<https://github.com/apache/beam/pull/36877>? I noticed this issue > has been open for a while. > > I've been analyzing the stack trace and the previous attempts by @liferoad< > https://github.com/liferoad> (e.g., #35576< > https://github.com/apache/beam/pull/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. > > — > Reply to this email directly, view it on GitHub< > https://github.com/apache/beam/issues/31422#issuecomment-3734107609>, or > unsubscribe< > https://github.com/notifications/unsubscribe-auth/BOEIQ337JITNOLKDXYLFMFL4GHV43AVCNFSM6AAAAAB5X5AYSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZUGEYDONRQHE>. > > You are receiving this because you were mentioned.Message ID: ***@***.***> > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/issues/31422#issuecomment-3734114281>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFAYJVLQ62JIC4QSAKOKB2D4GHWYPAVCNFSM6AAAAAB5X5AYSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZUGEYTIMRYGE> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> > -- 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]
