[jira] [Updated] (HBASE-8697) HBase MapReduce client should be able to retry if time out exception is encountered
[ https://issues.apache.org/jira/browse/HBASE-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changshu Liu updated HBASE-8697: Summary: HBase MapReduce client should be able to retry if time out exception is encountered (was: HBase client should be able to retry if time out exception is encountered when access region server) HBase MapReduce client should be able to retry if time out exception is encountered --- Key: HBASE-8697 URL: https://issues.apache.org/jira/browse/HBASE-8697 Project: HBase Issue Type: Improvement Components: Client Reporter: Changshu Liu Currently, timeoutexception is not retried if it occurred. We need to provide the mechanism to let user enable/config how to retry in this case. -- 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-8697) HBase MapReduce client should be able to retry if time out exception is encountered
[ https://issues.apache.org/jira/browse/HBASE-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changshu Liu updated HBASE-8697: Description: Currently, ScannerTimeOutException is not retried if it occurred in HBase client since it's derived from DoNotRetryException. We need to provide the mechanism to let user enable/config how to retry in this case when accessing HBase table rows using hadoop. (was: Currently, timeoutexception is not retried if it occurred. We need to provide the mechanism to let user enable/config how to retry in this case.) HBase MapReduce client should be able to retry if time out exception is encountered --- Key: HBASE-8697 URL: https://issues.apache.org/jira/browse/HBASE-8697 Project: HBase Issue Type: Improvement Components: Client Reporter: Changshu Liu Currently, ScannerTimeOutException is not retried if it occurred in HBase client since it's derived from DoNotRetryException. We need to provide the mechanism to let user enable/config how to retry in this case when accessing HBase table rows using hadoop. -- 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-8697) HBase MapReduce client should be able to retry if Scanner time out
[ https://issues.apache.org/jira/browse/HBASE-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Changshu Liu updated HBASE-8697: Summary: HBase MapReduce client should be able to retry if Scanner time out (was: HBase MapReduce client should be able to retry if time out exception is encountered) HBase MapReduce client should be able to retry if Scanner time out -- Key: HBASE-8697 URL: https://issues.apache.org/jira/browse/HBASE-8697 Project: HBase Issue Type: Improvement Components: Client Reporter: Changshu Liu Currently, ScannerTimeOutException is not retried if it occurred in HBase client since it's derived from DoNotRetryException. We need to provide the mechanism to let user enable/config how to retry in this case when accessing HBase table rows using hadoop. -- 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] [Created] (HBASE-8697) HBase client should be able to retry if time out exception is encountered when access region server
Changshu Liu created HBASE-8697: --- Summary: HBase client should be able to retry if time out exception is encountered when access region server Key: HBASE-8697 URL: https://issues.apache.org/jira/browse/HBASE-8697 Project: HBase Issue Type: Improvement Components: Client Reporter: Changshu Liu Currently, timeoutexception is not retried if it occurred. We need to provide the mechanism to let user enable/config how to retry in this case. -- 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
