[
https://issues.apache.org/jira/browse/HBASE-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640579#action_12640579
]
stack commented on HBASE-932:
-----------------------------
2008-10-17 10:26:25,374 FATAL org.apache.hadoop.hbase.regionserver.Flusher:
Replay of hlog required. Forcing server restart
In above case, regionserver wants to replay the WAL because flush failed
usually because hdfs is hosed. In above, could restart itself and perhaps all
would be well when it came back up (probably not though -- if hdfs is horked...
but hbase should try all the possibilities until admin shows up)
> Regionserver restart
> --------------------
>
> Key: HBASE-932
> URL: https://issues.apache.org/jira/browse/HBASE-932
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
>
> If we drop a flush or we fail close a write-ahead log, we currently shutdown
> the regionserver (we fail because of hdfs usually). Rather than shut
> themselves down, how about they restart? The restart at least in the
> HBASE-930 might fix the issue shaking DFSClient so it gets sense again. Even
> is HDFS is bad, it'll come around eventually. The HRS restarting itself plus
> HBASE-926 fix will make for fast recovery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
