[
https://issues.apache.org/jira/browse/HBASE-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chunhui shen updated HBASE-5528:
--------------------------------
Description:
In current log-splitting retry logic, it will retry forever if throws
IOException, I think we'd better change it to numbered times, and abort master
when retries exhausted.
was:
We will retry splitting log if failed in splitLogAfterStartup when master
starts.
However, there is no retry for failed splitting log in the process of
ServerShutdownHandler.
Also, if we finally failed to split log, we should abort master even if
filesystem is ok to prevent data loss.
Summary: Change retrying splitting log forever if throws IOException
to numbered times, and abort master when retries exhausted (was: Retry
splitting log if failed in the process of ServerShutdownHandler, and abort
master when retries exhausted)
> Change retrying splitting log forever if throws IOException to numbered
> times, and abort master when retries exhausted
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5528
> URL: https://issues.apache.org/jira/browse/HBASE-5528
> Project: HBase
> Issue Type: Bug
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: hbase-5528.patch, hbase-5528v2.patch, hbase-5528v3.patch
>
>
> In current log-splitting retry logic, it will retry forever if throws
> IOException, I think we'd better change it to numbered times, and abort
> master when retries exhausted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
