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 2022/04/18 03:07:00 UTC

[GitHub] [pulsar] dragonls opened a new issue, #15196: [broker] topic closed normally may still try to `closeFencedTopicForcefully`

dragonls opened a new issue, #15196:
URL: https://github.com/apache/pulsar/issues/15196

   **Describe the bug**
   Pulsar cluster with `topicFencingTimeoutSeconds`>0, the topic which is closed normally should not having the log `[A] Topic remained fenced for 10 seconds and is already closed (pendingWriteOps: 0)`.
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Deply a cluster with `topicFencingTimeoutSeconds` > 0, for example `topicFencingTimeoutSeconds=10`
   2. Trigger topic A to close normally
   3. `closeFencedTopicForcefully` still will be run, as `[A] Topic remained fenced for 10 seconds and is already closed (pendingWriteOps: 0)` will be printed.
   
   **Expected behavior**
   If topic A close normally, `[A] Topic remained fenced for 10 seconds and is already closed (pendingWriteOps: 0)` should not be logged.
   
   **Desktop (please complete the following information):**
    - OS: linux
    - Pulsar version: 2.8.3
   
   


-- 
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.apache.org

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

[GitHub] [pulsar] dragonls commented on issue #15196: [broker] topic closed normally may still try to `closeFencedTopicForcefully`

Posted by GitBox <gi...@apache.org>.

dragonls commented on issue #15196:
URL: https://github.com/apache/pulsar/issues/15196#issuecomment-1101085229

   Just a warning log, it is ok.


-- 
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] michaeljmarshall closed issue #15196: [broker] topic closed normally will also run `closeFencedTopicForcefully`

Posted by GitBox <gi...@apache.org>.

michaeljmarshall closed issue #15196: [broker] topic closed normally will also run `closeFencedTopicForcefully`
URL: https://github.com/apache/pulsar/issues/15196


-- 
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] dragonls closed issue #15196: [broker] topic closed normally may still try to `closeFencedTopicForcefully`

Posted by GitBox <gi...@apache.org>.

dragonls closed issue #15196: [broker] topic closed normally may still try to `closeFencedTopicForcefully`
URL: https://github.com/apache/pulsar/issues/15196


-- 
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