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
Send 3 normal messages
Msg received: Transaction msg with abort. seq: 1 ** // <----- should not be received **
Msg received: Transaction msg with commit. seq: 2
Msg received: Normal msg. seq: 0
Msg received: Normal msg. seq: 1
Msg received: Normal msg. seq: 2
Pulsar version:
Current version of pulsar is: 3.2.0 (standalone)
The text was updated successfully, but these errors were encountered:
SmileYun
changed the title
Cannot receive txn message after previous message be aborted
[Bug] Cannot receive txn message after previous message be aborted
Feb 27, 2024
I am encountering a similar issue. After calling abort, all messages in the topic get blocked. However, if I send a message that is not part of the transaction, the messages that were aborted still get consumed.
Has anyone encountered this issue before? How can I resolve this problem?
I am encountering a similar issue. After calling abort, all messages in the topic get blocked. However, if I send a message that is not part of the transaction, the messages that were aborted still get consumed.
Has anyone encountered this issue before? How can I resolve this problem?
Can the case you mentioned be stably reproduced by adding a single test in transaction_test?
Expected behavior
Actual behavior
Start a consumer
Output:
Send 3 normal messages (seq: 0,1,2)
Msg received: Normal msg. seq: 0
Msg received: Normal msg. seq: 1
Msg received: Normal msg. seq: 2
Send 3 txn messages (seq: 0: commit,1: abort, 2: commit)
Msg received: Transaction msg with commit. seq: 0
But also expect the message of seq 3 should be received.
producer log shown txn status is 4, 5, 4
2024/02/27 12:37:56 TxInfo 1 {0 64}
2024/02/27 12:37:56 Send msg 17.589083ms, 862:3:0,
2024/02/27 12:37:56 Txn be acked. 37.285584ms 4 {MostSigBits:0 LeastSigBits:64}
2024/02/27 12:37:56 Flush 4 {0 64}
2024/02/27 12:37:56 LastSequenceID 1709008676
2024/02/27 12:37:57 TxInfo 1 {0 65}
2024/02/27 12:37:57 Send msg 12.656042ms, 862:5:0,
2024/02/27 12:37:57 Txn be acked. 37.830083ms 5 {MostSigBits:0 LeastSigBits:65}
2024/02/27 12:37:57 Flush 5 {0 65}
2024/02/27 12:37:57 LastSequenceID 1709008677
2024/02/27 12:37:58 TxInfo 1 {0 66}
2024/02/27 12:37:58 Send msg 8.361125ms, 862:6:0,
2024/02/27 12:37:58 Txn be acked. 23.730334ms 4 {MostSigBits:0 LeastSigBits:66}
2024/02/27 12:37:58 Flush 4 {0 66}
2024/02/27 12:37:58 LastSequenceID 1709008678
INFO[0003] Closing producer producerID=1 producer_name=p-name topic="persistent://public/default/topic"
INFO[0003] Closed producer producerID=1 producer_name=p-name topic="persistent://public/default/topic"
Msg received: Transaction msg with abort. seq: 1 ** // <----- should not be received **
Msg received: Transaction msg with commit. seq: 2
Msg received: Normal msg. seq: 0
Msg received: Normal msg. seq: 1
Msg received: Normal msg. seq: 2
Steps to reproduce
// pseudo code
System configuration
Pulsar version:
Current version of pulsar is: 3.2.0 (standalone)
The text was updated successfully, but these errors were encountered: