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
Using pulsar-2.9.3, go-client-0.6.0
I enable batch in producer, keep produce message with auto-increment Id. Then Consumer receive message, write message to other database, individualAck message, this process is sync, make sure the message is write into database and ack success. There has no duplicated message, it's right. But when I execute consumer.close(), then restart it, there would occur several duplicated message with same Id at this point of time.
I have try setting config acknowledgmentAtBatchIndexLevelEnabled=true, duplicated message still occur. It seem the acked message has been redeliver to consumer when reconnecting.
Is duplicated message reasonable when client reconnect, although the message has been acked ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using pulsar-2.9.3, go-client-0.6.0
I enable batch in producer, keep produce message with auto-increment Id. Then Consumer receive message, write message to other database, individualAck message, this process is sync, make sure the message is write into database and ack success. There has no duplicated message, it's right. But when I execute consumer.close(), then restart it, there would occur several duplicated message with same Id at this point of time.
I have try setting config acknowledgmentAtBatchIndexLevelEnabled=true, duplicated message still occur. It seem the acked message has been redeliver to consumer when reconnecting.
Is duplicated message reasonable when client reconnect, although the message has been acked ?
Beta Was this translation helpful? Give feedback.
All reactions