reuvenlax commented on PR #27495: URL: https://github.com/apache/beam/pull/27495#issuecomment-1648775277
yes, but Beam code creates a new stream when it hits this issue. On Mon, Jul 24, 2023 at 2:56 PM scwhittle ***@***.***> wrote: > We should try to dive deeper into this pipeline that got stuck, as it > sounds like we don't understand what happened and there's no reason to > believe that retrying the work item will be any different than simply > retrying the call. > > @reuvenlax <https://github.com/reuvenlax> I believe the issue with the > stuck pipeline was that there was active processing for the key on two > different workers. These keys were competing for the stream and were > repeatedly invalidating each other. Only one of the keys was still valid in > the backend and if the stale key stopped processing, the still active key > should have completed (or would complete on a full retry). > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/pull/27495#issuecomment-1648680997>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFAYJVPXAVTWTDWCANEV4VLXR3VP3ANCNFSM6AAAAAA2JSTZ3A> > . > You are receiving this because you were mentioned.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]
