You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the new goroutine blocks indefinitely or takes a long time to execute, you could run into a goroutine leak and/or lock contention. is this a concern?
closing relistStopChan without checking whether it has already been closed
We should modify the replay code to:
prevent any snowballing from the goroutines by waiting on the child goroutine to be closed, rather than being optimistic that it will close eventually
make the backofff exponential retry-er aware of the kill switch(es) in order to fail fast and not be blocked on the exponential backoff retry-er trying to complete work that we don't want to happen anymore.
The text was updated successfully, but these errors were encountered:
In support of the sync set proposal
There were some outstanding concerns raised on #2852
In particular,
We should modify the replay code to:
The text was updated successfully, but these errors were encountered: