lostluck commented on issue #33815: URL: https://github.com/apache/beam/issues/33815#issuecomment-2819378074
Offhand, that stack trace looks normal. One thread is updating the stage watermarks, (which requires holding the ElementManager condition lock, and the stage's personal lock) and PersistBundle is waiting on that lock to write to the a stage's state. A question here is which stages are being locked up (are they the same lock?). Very interesting that Python has different behaviour here, and might be pointing to a Go SDK side bug, if it's not an issue with Prism. -- 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: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
