[GitHub] [pulsar] ericsyh opened a new issue #13480: [bug](zkclient): ledger znode delete incomplete when broker delete topic

[GitBox]

ericsyh opened a new issue #13480:
URL: https://github.com/apache/pulsar/issues/13480


   **Describe the bug**
   On pulsar 2.8.1, we found in some corner case zkclient clean ledger znode is 
incomplete when broker deleting the topic. The data in target ledger znode is 
clean but the znode still exists which leads bk audit parse ledger metadata 
error then exit the bk process.
   
   * listledgers can get the ledger id 278117
   
   <img width="878" alt="截屏2021-12-24 上午10 37 28" 
src="https://user-images.githubusercontent.com/10498732/147311107-1fc629c7-2bd4-4e6d-8fb9-58ea0cb7d71f.png";>
   
   * ledgermetadata will get error to parse the ledger metadata
   
   <img width="1004" alt="截屏2021-12-24 上午10 37 44" 
src="https://user-images.githubusercontent.com/10498732/147311228-3c8a4bef-d7f6-4d8b-95b8-4526e8290a18.png";>
   
   * check the zk and we found znode exists but znode data is clean
   <img width="372" alt="截屏2021-12-24 上午10 39 13" 
src="https://user-images.githubusercontent.com/10498732/147311319-c372fc9d-0151-4850-8217-9efb4f42b734.png";>
   
   **To Reproduce**
   It's not easy to reproduce, we guess that it happens when zk has some 
abnormal situations. But sadly the zk cluster has no monitor and log level is 
not debug, we cannot locate the problem in zk.
   
   **Expected behavior**
   Hope pulsar zkclient can have some enhancements to avoid this case. 
   


-- 
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-unsubscr...@pulsar.apache.org

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