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
When client enable AckWithResponse option, an AckResponse command is expected to receive from broker after an AckRequest command.
Actual behavior
No AckResponse command received until client request time out. Factly, in broker side, AckResponse is supported only when connection ProtocolVersion is or above 17 and requestId is set in AckRequest.
INFO[0000] [Connecting to broker] remote_addr="pulsar://localhost:6650"
INFO[0000] [TCP connection established] local_addr="127.0.0.1:38574" remote_addr="pulsar://localhost:6650"
INFO[0000] [Connection is ready] local_addr="127.0.0.1:38574" remote_addr="pulsar://localhost:6650"
INFO[0000] Lookup result: &{LogicalAddr:pulsar://localhost:6650 PhysicalAddr:pulsar://localhost:6650} consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
INFO[0000] [Connected consumer] consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
INFO[0000] Created consumer with queueCh cap [1000], len [0] queueSize [1000] consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
INFO[0000] [get into runEventsLoop] consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
INFO[0000] [dispatcher received connection event] consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
INFO[0000] dispatcher requesting initial permits=1000 consumerID=1 name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
Received message msgId: pulsar.trackingMessageID{messageID:pulsar.messageID{ledgerID:267, entryID:10, batchIdx:0, partitionIdx:0}, tracker:(*pulsar.ackTracker)(nil), consumer:(*pulsar.partitionConsumer)(0xc000162000), receivedTime:time.Time{wall:0xc09c38b1c9a0a930, ext:3726914057, loc:(*time.Location)(0x106e4a0)}} -- content: 'hello-0'
ERRO[0033] [Ack with response error] consumerID=1 error="request timed out" name=twpkx subscription=my-sub topic="persistent://public/default/topic-0-partition-0"
request timed out
Steps to reproduce
Subscribe topics with ConsumerOptions AckWithResponse option set true.
System configuration
Pulsar version: 2.9
The text was updated successfully, but these errors were encountered:
Expected behavior
When client enable AckWithResponse option, an AckResponse command is expected to receive from broker after an AckRequest command.
Actual behavior
No AckResponse command received until client request time out. Factly, in broker side, AckResponse is supported only when connection ProtocolVersion is or above 17 and requestId is set in AckRequest.
Steps to reproduce
Subscribe topics with ConsumerOptions AckWithResponse option set true.
System configuration
Pulsar version: 2.9
The text was updated successfully, but these errors were encountered: