You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Tak Lon (Stephen) Wu (JIRA)" <ji...@apache.org> on 2018/04/12 18:39:00 UTC
[jira] [Created] (HBASE-20400) Make `MAX_WAIT` and
`waitIfNotFinished` in CleanerContext configurable
Tak Lon (Stephen) Wu created HBASE-20400:
--------------------------------------------
Summary: Make `MAX_WAIT` and `waitIfNotFinished` in CleanerContext configurable
Key: HBASE-20400
URL: https://issues.apache.org/jira/browse/HBASE-20400
Project: HBase
Issue Type: Improvement
Components: master, Performance
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 make a configuration property for waitIfNotFinished when LogClearner call getResult.
1. 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
2. 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
(v7.6.3#76005)