mnit016 opened a new issue, #4100:
URL: https://github.com/apache/bookkeeper/issues/4100

   **BUG REPORT**
   
   ***Somehow 1 bookie in cluster is full ledger disk and turned to read-only 
mode***
   Hi there, I'm facing a issue in Pulsar-2.9.5, bookie ledger usage increased 
to 99.9%. Similar with 
[#1908](https://github.com/apache/bookkeeper/issues/1908), but I can't see any 
ledger information in error logs there to do clean up.
   
![image](https://github.com/apache/bookkeeper/assets/37934995/f8dfbec1-ff88-4d17-aa01-6060222e9c0d)
   
   ***To Reproduce***
   <N/A>
   
   ***Expected behavior***
   How could I get over this issue? any workaround / solution for this?
   
   ***Screenshots***
   Through Splunk, from several days ago, a lot of "**Entering Safepoint 
region**..." "**Leaving safepoint region**..." appear in logs
   After a day, I found this "**Exception ledger flush**" / "**Error in Rocksdb 
put**" starting
   
![image](https://github.com/apache/bookkeeper/assets/37934995/9c73541f-a7f3-48b3-8d4f-e4dc8d950fcc)
   And 4 hours later, it turned to "**Error during flush**"
   
![image](https://github.com/apache/bookkeeper/assets/37934995/0c56cffc-7ac9-4a8e-9236-c200354fea60)
   Above logs happen until "**Ledger directory ... is out-of-space**" and 
continuos
   
![image](https://github.com/apache/bookkeeper/assets/37934995/3ffc78c1-4776-45ee-941b-9432eefa8268)
   
   ***Additional context***
   Pulsar 2.9.5 - K8s 1.26.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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to