[fix][broker] fix replicated subscriptions for transactional messages#22452
Conversation
|
PTAL, thanks. @BewareMyPower @poorbarcode @codelipenghui @liangyepianzhou |
BewareMyPower
left a comment
There was a problem hiding this comment.
Could you add a test for it?
Added, PTAL, thanks. |
|
@thetumbled You need to add a test related to transaction, right? |
|
e27fd14 to
6fae3a3
Compare
|
/pulsarbot rerun-failure-checks |
1 similar comment
|
/pulsarbot rerun-failure-checks |
Pulsar CI / CI - Unit - Brokers - Broker Group 1 (pull_request) test is not stable, please check the reason |
I have fixed the test code, please help to trigger the CI again, thanks. |
|
/pulsarbot rerun-failure-checks |
2 similar comments
|
/pulsarbot rerun-failure-checks |
|
/pulsarbot rerun-failure-checks |
|
@poorbarcode any more change requests? |
|
PTAL, thanks. @poorbarcode |
…apache#22452) (cherry picked from commit 9fd1b61) (cherry picked from commit e300fbd)
…apache#22452) (cherry picked from commit 9fd1b61) (cherry picked from commit e300fbd)
Motivation
In non-transactional production, we update the
LastDataMessagePublishedTimestampwhen the message is persisted successfully. But in transactional production, we do not updateLastDataMessagePublishedTimestamp, which will impact the featureReplicatedSubscription.Modifications
Update the
LastDataMessagePublishedTimestampwhen the max read position move forward.Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: thetumbled#45