Tak Lon (Stephen) Wu created HBASE-20401:

             Summary: Make `MAX_WAIT` and `waitIfNotFinished` in CleanerContext 
                 Key: HBASE-20401
                 URL: https://issues.apache.org/jira/browse/HBASE-20401
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 2.0.0-beta-1, 3.0.0, 1.5.0, 1.4.4, 2.0.0
            Reporter: Tak Lon (Stephen) Wu

When backporting HBASE-18309 in HBASE-20352, the deleteFiles calls 
CleanerContext.java#getResult with a waitIfNotFinished timeout to wait for 
notification (notify) from the fs.delete file thread. there might be two 
situation need to tune the MAX_WAIT in CleanerContext or waitIfNotFinished when 
LogClearner call getResult.
 # fs.delete never complete (strange but possible), then we need to wait for a 
max of 60 seconds. here, 60 seconds might be too long
 # getResult is waiting in the period of 500 milliseconds, but the fs.delete 
has completed and setFromClear is set but yet notify(). one might want to tune 
this 500 milliseconds to 200 or less .

This message was sent by Atlassian JIRA

Reply via email to