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

   **BUG REPORT**
   
   ***Describe the bug***
   Whenever major or minor compaction runs, it does not remove the log files 
which has utilised more than threshold value. But only remove the files with 
usage < threshold.
   
   A clear and concise description of what the bug is.
   I am seeing high disk usage in ledger directory in 3 bookie cluster, all 3 
nodes have couple of log files with size 1.1GB which is the default max entry 
log file size before it creates a new one. 
   As per the documentation 
[here](https://bookkeeper.apache.org/docs/reference/config/) for Major and 
Minor Compaction, it is supposed to delete the log files when remaining log 
file size reaches below threshold.
   When trying to debug this in code found that condition is checking for 
meta.Usage > threshold and ignore the meta file which is supposed to get 
deleted, what I feel it should be checking the meta.Remaining > Threshold. 
   
https://github.com/apache/bookkeeper/blob/dd80e967e7d3dc6873231a7bc04feaba83be54c3/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/GarbageCollectorThread.java#L573
   
   ***To Reproduce***
   
   Steps to reproduce the behavior:
   1. Go to '...'
   2. Click on '....'
   3. Scroll down to '....'
   4. See error
   
   ***Expected behavior***
   A clear and concise description of what you expected to happen.
   - Compaction should have removed the file if remaining file size < threshold.
   
   ***Screenshots***
   
   If applicable, add screenshots to help explain your problem.
   <img width="1431" alt="Screenshot 2022-12-22 at 1 02 33 PM" 
src="https://user-images.githubusercontent.com/70515711/209081185-ed9723f2-06fa-4974-8c42-4d9ddbb13e10.png";>
   
   ***Additional context***
   Add any other context about the problem here.
   


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