[
https://issues.apache.org/jira/browse/HBASE-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600969#comment-13600969
]
nkeywal commented on HBASE-8081:
--------------------------------
Added to this, there are a lot of critical scenarios that you can have without
separated logs:
- some blocks in the WAL may be not recoverable (corrupted, too many boxes
missing). This risk is highly mitigated with a separate log. Without this, the
whole cluster becomes unavailable when you're unlucky.
- if you come into hdfs issues during the recovery (hdfs issue being going to a
dead datanode, something highly probable during a recovery), the recovery will
be much slower.
- trying to run a recovery while .meta. is not available is also problematic.
Unsuring that .meta. comes back early simplifies a lot of critical scenarios.
So having this in 0.94 is 'interesting' I would say :-).
> Backport HBASE-7213 (separate hlog for meta tables) to 0.94
> -----------------------------------------------------------
>
> Key: HBASE-8081
> URL: https://issues.apache.org/jira/browse/HBASE-8081
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.5
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.94.7
>
> Attachments: 7213-0.94-2.patch, 7213-0.94.patch
>
>
> I am interested in backporting HBASE-7213 to 0.94. Helps to address more of
> the MTTR story. Offline discussion with Lars indicated he is interested as
> well.
--
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
