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
Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state #12754
Labels
type/bug
The PR fixed a bug or issue reported a bug
Comments
@congbobo184 PTAL |
@congbobo184 it may be a regression introduced by #11934 Here I see that a message is being sent, pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java Line 1135 in 8551868
|
@gaoran10 PTAL as well |
congbobo184
added a commit
that referenced
this issue
Nov 12, 2021
fix #12754 ### Motivation Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE ### Modifications judge NPE logic
eolivelli
pushed a commit
to eolivelli/pulsar
that referenced
this issue
Nov 29, 2021
…#12758) fix apache#12754 ### Motivation Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE ### Modifications judge NPE logic
eolivelli
pushed a commit
to eolivelli/pulsar
that referenced
this issue
Mar 1, 2022
…#12758) fix apache#12754 Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE judge NPE logic (cherry picked from commit c90c89b)
eolivelli
pushed a commit
to eolivelli/pulsar
that referenced
this issue
Mar 1, 2022
…#12758) fix apache#12754 Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE judge NPE logic (cherry picked from commit c90c89b)
eolivelli
pushed a commit
to datastax/pulsar
that referenced
this issue
Mar 1, 2022
…#12758) fix apache#12754 Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE judge NPE logic (cherry picked from commit c90c89b)
eolivelli
pushed a commit
to datastax/pulsar
that referenced
this issue
Mar 1, 2022
…#12758) fix apache#12754 Now when delete topic, we will write a null value to Transaction buffer snapshot topic, other topic recover by this transaction buffer snapshot system topic, will produce NPE judge NPE logic (cherry picked from commit c90c89b) (cherry picked from commit 75cec6d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I found this problem while testing Pulsar 2.9.0rc3 and running the unit tests of Pulsar JMS (http://github.com/datastax/pulsar-jms).
When you enable the TransactionCoordinator deleting a topic forcefully leaves the broker in such a bad state that it is no more possible to consume data from other topics.
To Reproduce
Expected behavior
The second topic works well
Additional context
The problem is present in 2.9.0rc3 but NOT in Pulsar 2.8.1
Running on JDK8/Mac
The text was updated successfully, but these errors were encountered: