[
https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8449:
-------------------------
Description:
HBASE-8359 is an interesting issue that roams near and far. This issue is
about making use of the findings handily summarized on the end of hbase-8359
which have it that trunk needs refactor around how it does its recoverLease
handling (and that the patch committed against HBASE-8359 is not what we want
going forward).
This issue is about making a patch that adds a lag between recoverLease
invocations where the lag is related to dfs timeouts -- the hdfs-side dfs
timeout -- and optionally makes use of the isFileClosed API if it is available
(a facility that is not yet committed to a branch near you and unlikely to be
within your locality with a good while to come).
was:
HBASE-8354 is an interesting issue that roams near and far. This issue is
about making use of the findings handily summarized on the end of hbase-8354
which have it that trunk needs refactor around how it does its recoverLease
handling (and that the patch committed against HBASE-8354 is not what we want
going forward).
This issue is about making a patch that adds a lag between recoverLease
invocations where the lag is related to dfs timeouts -- the hdfs-side dfs
timeout -- and optionally makes use of the isFileClosed API if it is available
(a facility that is not yet committed to a branch near you and unlikely to be
within your locality with a good while to come).
> Refactor recoverLease retries and pauses informed by findings over in
> hbase-8389
> --------------------------------------------------------------------------------
>
> Key: HBASE-8449
> URL: https://issues.apache.org/jira/browse/HBASE-8449
> Project: HBase
> Issue Type: Bug
> Components: Filesystem Integration
> Affects Versions: 0.94.7, 0.95.0
> Reporter: stack
> Priority: Critical
> Fix For: 0.95.1
>
>
> HBASE-8359 is an interesting issue that roams near and far. This issue is
> about making use of the findings handily summarized on the end of hbase-8359
> which have it that trunk needs refactor around how it does its recoverLease
> handling (and that the patch committed against HBASE-8359 is not what we want
> going forward).
> This issue is about making a patch that adds a lag between recoverLease
> invocations where the lag is related to dfs timeouts -- the hdfs-side dfs
> timeout -- and optionally makes use of the isFileClosed API if it is
> available (a facility that is not yet committed to a branch near you and
> unlikely to be within your locality with a good while to come).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
