[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449v7.txt 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 Assignee: stack Priority: Critical Fix For: 0.95.1 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt, 8449v4.txt, 8449v6.txt, 8449v7.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Resolution: Fixed Fix Version/s: 0.98.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Resolved. Committed to 0.95 and trunk so it is in place for 0.95.1 and we can see how it does under duress. 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 Assignee: stack Priority: Critical Fix For: 0.98.0, 0.95.1 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt, 8449v4.txt, 8449v6.txt, 8449v7.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449v2.txt Here is a patch w/ a first test. Will add more in subsequent tests. Also tries to use isFileClosed if available, hbase-8394. 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 Attachments: 8449.txt, 8449v2.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449v3.txt Here is a patch. Has tests. Will try and make use of isFileClosed if available. 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 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Assignee: stack Status: Patch Available (was: Open) 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.95.0, 0.94.7 Reporter: stack Assignee: stack Priority: Critical Fix For: 0.95.1 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449v4.txt Fix my test (oops) 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 Assignee: stack Priority: Critical Fix For: 0.95.1 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt, 8449v4.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449v6.txt Address nkeywal find. 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 Assignee: stack Priority: Critical Fix For: 0.95.1 Attachments: 8449.txt, 8449v2.txt, 8449v3.txt, 8449v4.txt, 8449v6.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8449: - Attachment: 8449.txt Here is a start. Needs test and testing on cluster. 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 Attachments: 8449.txt 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ 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
[jira] [Updated] (HBASE-8449) Refactor recoverLease retries and pauses informed by findings over in hbase-8389
[ https://issues.apache.org/jira/browse/HBASE-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Sharma updated HBASE-8449: Summary: Refactor recoverLease retries and pauses informed by findings over in hbase-8389 (was: Refactor recoverLease retries and pauses informed by findings over in hbase-8354) 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-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). -- 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
