kellen

Similar issue, probably same root cause: when using a lock to mutate shared state, if the lock is acquired when a reload starts, the new process can never be `join`ed,...

@mattwelke Error reproduction always appreciated!

My implicit class version of this in our repo is called `avroFiles` (plural). No collision issue.

May not be tractable per description in #3969

Ready for re-review and/or further comments @clairemcginty @RustedBones

@regadas any ideas on how we might restructure this to fit better w/ the rest of the architecture?

Moving to 0.12.1 as this is not yet fixed in beam

@AntonOfTheWoods no, I added redis as the backend instead.

It appears the strapdownjs.com domain has expired and the project is stale/dead. We'll need to either vendor this code or move to another lib. Version we refer to is here:...

@lukecwik We (spotify) are seeing `ConcurrentModificationException` errors due to this PR. The issue starts in [WriteFiles.java](https://github.com/apache/beam/blame/master/sdks/java/core/src/main/java/org/apache/beam/sdk/io/WriteFiles.java#L964) where you construct a new future, then clear the existing `closeFuture`s. I think the...