SabyasachiDasTR commented on issue #7600:
URL: https://github.com/apache/hudi/issues/7600#issuecomment-1378651450

   Hi @xushiyan we enabled hudi debug logging and scanned all the container 
logs. We did not find any ERROR or WARN logs related to 'clean'. Below are the 
info logs and looks like it is not able to find the point in time from where it 
has to clean. 
   What could be the reason? 
   
   FYI we did try 'cleans run' command in one of our table and it executed 
successfully and cleaned lot of files. But the auto clean is still not 
triggering in any of the tables, that eventually is causing the number of log 
files to grow.
   
   `stderr.2023-01-09-10:2023-01-09T11:47:59.346+0000 [INFO] 
[1673249876388qa_correlation_id] [org.apache.hudi.client.BaseHoodieWriteClient] 
[BaseHoodieWriteClient]: Start to clean synchronously.
   stderr.2023-01-09-10:2023-01-09T11:48:00.062+0000 [INFO] 
[1673249876388qa_correlation_id] [org.apache.hudi.client.BaseHoodieWriteClient] 
[BaseHoodieWriteClient]: Scheduling cleaning at instant time :20230109114759346
   stderr.2023-01-09-10:2023-01-09T11:48:01.308+0000 [INFO] 
[1673249876388qa_correlation_id] 
[org.apache.hudi.table.action.clean.CleanPlanner] [CleanPlanner]: No earliest 
commit to retain. No need to scan partitions !!
   stderr.2023-01-09-10:2023-01-09T11:48:01.308+0000 [INFO] 
[1673249876388qa_correlation_id] 
[org.apache.hudi.table.action.clean.CleanPlanner] [CleanPlanner]: Nothing to 
clean here. It is already clean`
   
   As per the logs Nothing to clean here. It is already clean , but we do see 
lot of logs files from 2 months back.
   I have attached generic logs here.
   
[AllErrorLogs.txt](https://github.com/apache/hudi/files/10392060/AllErrorLogs.txt)
   
   
[AllWARNLogs.txt](https://github.com/apache/hudi/files/10392070/AllWARNLogs.txt)
   
   
[HudiErrorLogs.txt](https://github.com/apache/hudi/files/10392074/HudiErrorLogs.txt)
   
   
[HudiWARNLogs.txt](https://github.com/apache/hudi/files/10392075/HudiWARNLogs.txt)
   
   


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