dtspence commented on issue #4485:
URL: https://github.com/apache/accumulo/issues/4485#issuecomment-2072890673

   @dlmarion 
   > is it the case that you manually cancelled the compactions? If so, did 
your command complete, or did it hang too?
   
   No, the compaction eventually logs that it has canceled. We have not been 
taking manual intervention.
   
   > The FileCompactor 
[checks](https://github.com/apache/accumulo/blob/2.1/server/base/src/main/java/org/apache/accumulo/server/compaction/FileCompactor.java#L421)
 if the compaction is still enabled for every key that it writes. I'm curious 
if the compaction was making progress (you said filtering was not expected 
which could also be a cause). Is this happening often? If not, is bouncing the 
tserver an option?
   
   Yes, the issue is re-appearing. It does not appear to be localized to a 
single t-server. We have been wondering if something tablet related that 
correlates to the issue. At least one tablet we were looking at was a hot-spot 
and contained a lot of i-files from imports. 


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