-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix][broker] fix replicated subscriptions for transactional messages #22452
[fix][broker] fix replicated subscriptions for transactional messages #22452
Conversation
PTAL, thanks. @BewareMyPower @poorbarcode @codelipenghui @liangyepianzhou |
...r/src/main/java/org/apache/pulsar/broker/transaction/buffer/impl/TopicTransactionBuffer.java
Outdated
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a test for it?
Added, PTAL, thanks. |
@thetumbled You need to add a test related to transaction, right? |
|
pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java
Outdated
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java
Outdated
Show resolved
Hide resolved
e27fd14
to
6fae3a3
Compare
...r/src/test/java/org/apache/pulsar/broker/service/TransactionalReplicateSubscriptionTest.java
Show resolved
Hide resolved
…estamp # Conflicts: # pulsar-broker/src/main/java/org/apache/pulsar/broker/transaction/buffer/impl/TopicTransactionBuffer.java # pulsar-broker/src/test/java/org/apache/pulsar/broker/transaction/TransactionTest.java
/pulsarbot rerun-failure-checks |
1 similar comment
/pulsarbot rerun-failure-checks |
...r/src/main/java/org/apache/pulsar/broker/transaction/buffer/impl/TopicTransactionBuffer.java
Show resolved
Hide resolved
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
LastDataMessagePublishedTimestamp
when the message is persisted successfully. But in transactional production, we do not updateLastDataMessagePublishedTimestamp
, which will impact the featureReplicatedSubscription
.Modifications
Update the
LastDataMessagePublishedTimestamp
when 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
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: thetumbled#45