You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/11/11 13:08:59 UTC

[GitHub] [pulsar] eolivelli opened a new issue #12754: Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

eolivelli opened a new issue #12754:
URL: https://github.com/apache/pulsar/issues/12754


   **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**
   - Start one Broker and setup Transactions
   - Create one topic in public/default
   - Create one subscription on the topic
   - Delete the topic with "force" = true
   - Create another topic with a different name (in the same namespace)
   - Create one subscription on the second topic
   - Produce a message to the second topic
   - Try to receive a message from the second topic, Consumer.receive() will hang forever
   
   **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 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar] congbobo184 closed issue #12754: Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

Posted by GitBox <gi...@apache.org>.
congbobo184 closed issue #12754:
URL: https://github.com/apache/pulsar/issues/12754


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar] eolivelli commented on issue #12754: Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

Posted by GitBox <gi...@apache.org>.
eolivelli commented on issue #12754:
URL: https://github.com/apache/pulsar/issues/12754#issuecomment-966298204


   @gaoran10 PTAL as well


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar] eolivelli commented on issue #12754: Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

Posted by GitBox <gi...@apache.org>.
eolivelli commented on issue #12754:
URL: https://github.com/apache/pulsar/issues/12754#issuecomment-966297885


   @congbobo184  it may be a regression introduced by #11934
   
   Here I see that a message is being sent,
   that's the main difference in the deleteTopic code path in case of force=true and transactions enabled
   
   https://github.com/apache/pulsar/blob/8551868468327cc04ca6d4e9fe4bcb718ad38cbc/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L1135
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar] eolivelli commented on issue #12754: Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

Posted by GitBox <gi...@apache.org>.
eolivelli commented on issue #12754:
URL: https://github.com/apache/pulsar/issues/12754#issuecomment-966289011


   @congbobo184 PTAL


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org