[
https://issues.apache.org/jira/browse/HBASE-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224007#comment-13224007
]
ramkrishna.s.vasudevan commented on HBASE-5528:
-----------------------------------------------
@Chunhui
We have faced scenarios where the IOException soemtimes gets thrown when the DN
goes down or when a switch happens in NN (Hadoop 0.20 + append is the version
we use) .
In that case the retry logic should work.
Only if the NN is not available then we may make the master abort.
If we abort the master, one thing has to be ensured that when the master comes
up again or the back up master comes up the same problem should not happen.
> 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
