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
There could be a case when the channel is not needed and the overflow is present, but it should be dropped.
The current solution is to pipe all the overflow from via dmqcli to /dev/null. However, this is just a workaround, since dmqcli is not intended to be use as the administrative application, so it doesn't have this features.
It also brings the problem with the subscribers - dmqcli doesn't currently support subscibers, so there's no way to drain the subscriber based channel.
It seems better, now when we have the unix control socket, just to issue an command and make dmqnode to drop the channel including the overflow.
The text was updated successfully, but these errors were encountered:
There could be a case when the channel is not needed and the overflow is present, but it should be dropped.
The current solution is to pipe all the overflow from via dmqcli to
/dev/null
. However, this is just a workaround, sincedmqcli
is not intended to be use as the administrative application, so it doesn't have this features.It also brings the problem with the subscribers -
dmqcli
doesn't currently support subscibers, so there's no way to drain the subscriber based channel.It seems better, now when we have the unix control socket, just to issue an command and make dmqnode to drop the channel including the overflow.
The text was updated successfully, but these errors were encountered: