You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2020/03/03 17:03:28 UTC

[GitHub] [accumulo] EdColeman commented on issue #1534: GarbageCollectorIT.gcLotsOfCandidatesIT failure

EdColeman commented on issue #1534: GarbageCollectorIT.gcLotsOfCandidatesIT failure
URL: https://github.com/apache/accumulo/issues/1534#issuecomment-594058617
 
 
   Could there be a race condition with the shutdown?  From one of the stack traces it seemed to hint that the gc was shutdown (which should remove the lock) and then the clean-up is trying to delete the now non-existant lock.
   
   If that is the case, then if gc shutdown is called, the delete could accept that the lock has already been removed by catching / ignoring the node does not exist exception.
   
   Or, is this test also trying to validate the gc behavior w.r.t. losing the lock?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services