hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-20401) Make `MAX_WAIT` and `waitIfNotFinished` in CleanerContext configurable
Date Fri, 13 Apr 2018 06:10:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Busbey updated HBASE-20401:
--------------------------------
    Labels: beginner  (was: easyfix newbie)

> Make `MAX_WAIT` and `waitIfNotFinished` in CleanerContext configurable
> ----------------------------------------------------------------------
>
>                 Key: HBASE-20401
>                 URL: https://issues.apache.org/jira/browse/HBASE-20401
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 3.0.0, 1.5.0, 2.0.0-beta-1, 1.4.4, 2.0.0
>            Reporter: Tak Lon (Stephen) Wu
>            Priority: Minor
>              Labels: beginner
>
> 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
(v7.6.3#76005)

Mime
View raw message