When the client uses the Consume operator, then they should also provide an entity that consumes the output. If there is no consumer, then the worker pool will halt, due to being blocked on not being able to send. When the entire output buffer is full, no worker can continue. There should be some kind of warning mechanism to indicate as such and or a timeout at which point the pool should close down gracefully and the traverse result should include an appropriate error (missing output consumer)
When the client uses the Consume operator, then they should also provide an entity that consumes the output. If there is no consumer, then the worker pool will halt, due to being blocked on not being able to send. When the entire output buffer is full, no worker can continue. There should be some kind of warning mechanism to indicate as such and or a timeout at which point the pool should close down gracefully and the traverse result should include an appropriate error (missing output consumer)