[
https://issues.apache.org/jira/browse/HBASE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402863#comment-13402863
]
Jesse Yates commented on HBASE-2611:
------------------------------------
@Himanshu here is the thread I started on this on dev@ little while ago:
http://search-hadoop.com/m/u2D7j1yRpi72
It basically comes down to the fact that it would be irresponsible to do a
release of HBase that requires an unstable dependency. Yeah, TM has it in
production, but that doesn't mean their usage is representative of
_everyone's_. If the ZK fellas decide that 3.4 is a stable release, then I'm
all for making it the requirement in 0.96, but until the guys who write the
software feel like its stable, I don't think we are qualified to say it is
stable.
I do think its weird that we make 3.4 a dependency, but it really would be too
weird (and honestly a waste of effort) to support two versions of the protocol,
especially considering the trickiness of dealing with ZK clusters that may be
in the process of upgrade, etc.
> Handle RS that fails while processing the failure of another one
> ----------------------------------------------------------------
>
> Key: HBASE-2611
> URL: https://issues.apache.org/jira/browse/HBASE-2611
> Project: HBase
> Issue Type: Sub-task
> Components: replication
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Attachments: HBase-2611-upstream-v1.patch
>
>
> HBASE-2223 doesn't manage region servers that fail while doing the transfer
> of HLogs queues from other region servers that failed. Devise a reliable way
> to do it.
--
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
