[
https://issues.apache.org/jira/browse/HBASE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439843#comment-13439843
]
nkeywal commented on HBASE-5320:
--------------------------------
I think that the server states should be exposed to the client in ZK. Not only
a high level "cluster status", but the state of every RS.
There are limitations in ZK today so it's not ideal (could not scale with x000
clients), but exposing these states is typically implemented with multicast
messages with the client having a read only access (while a ZK connection
allows to write as well today).
> Create client API to handle HBase maintenance gracefully
> --------------------------------------------------------
>
> Key: HBASE-5320
> URL: https://issues.apache.org/jira/browse/HBASE-5320
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Minor
>
> When we do HBase cluster maintenance, we typically have to manually stop or
> disable the client temporarily. It would be nice to have a way for the client
> to find out that HBase in undergoing maintenance through an appropriate API
> and gracefully handle it on its own.
--
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
