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 you have a Queue writing to a Channel and call close on the Queue, Queue.Close will block on writing to Channel.Write. This is because the Close waits on the shutdown condition of the Queue.
Should queues be able to drop the held messages when stopped if configured to do so? I mean, use an additional parameter that instructs the queues to drop their messages either instantly or after some time when they are closed so that the next sink in the pipeline can be closed in a "time-deterministic" fashion.
If you have a
Queue
writing to aChannel
and call close on theQueue
,Queue.Close
will block on writing toChannel.Write
. This is because theClose
waits on the shutdown condition of theQueue
.Please see containerd/containerd#1254 for the mitigation for this.
The text was updated successfully, but these errors were encountered: