[
https://issues.apache.org/jira/browse/HBASE-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092698#comment-13092698
]
Andrew Purtell commented on HBASE-4274:
---------------------------------------
Doesn't HBASE-4222 already address this? It takes a different approach, and
arguably a better one. No need to abort if a new HLog pipeline can be
established.
> RS should periodically ping its HLog pipeline even if no writes are arriving
> ----------------------------------------------------------------------------
>
> Key: HBASE-4274
> URL: https://issues.apache.org/jira/browse/HBASE-4274
> Project: HBase
> Issue Type: Improvement
> Components: regionserver, wal
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 0.92.0
>
>
> If you restart HDFS underneath HBase, when HBase isn't taking any write load,
> the region servers won't "notice" that there's any problem until the next
> time they take a write, at which point they will abort (because the pipeline
> is gone from beneath them). It would be better if they wrote some garbage to
> their HLog once every few seconds as a sort of keepalive, so they will
> aggressively abort as soon as there's an issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
