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 producer.Close are called,it will close within configured OperationTimeout
Actual behavior
producer.Close may block forever and won't time out after configured OperationTimeout
Steps to reproduce
Just run the perf program for a while and send SIGINT or ctrl+c to it. This situation may be triggered.
This is because the callback of producer.SendAsyc contains a send behavior on a channel which under the same scope with stopCh. When we trigger producer.Close, if case <-stop: happens before case latency := <-ch:, it will block forever because it may be block at here and RequestOnCnx has no time out guarantee.
System configuration
Pulsar version: any
The text was updated successfully, but these errors were encountered:
Original Issue: apache#491
Expected behavior
If producer.Close are called,it will close within configured OperationTimeout
Actual behavior
producer.Close may block forever and won't time out after configured OperationTimeout
Steps to reproduce
Just run the perf program for a while and send SIGINT or ctrl+c to it. This situation may be triggered.
This is because the callback of producer.SendAsyc contains a send behavior on a channel which under the same scope with stopCh. When we trigger producer.Close, if
case <-stop:
happens beforecase latency := <-ch:
, it will block forever because it may be block at here and RequestOnCnx has no time out guarantee.System configuration
Pulsar version: any
The text was updated successfully, but these errors were encountered: