[
https://issues.apache.org/jira/browse/HBASE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198591#comment-13198591
]
Mikhail Bautin commented on HBASE-5320:
---------------------------------------
Lars: collaboration would be very welcome :) I do not yet have a design in mind
for this one, nor have I started actively working on this. I just noticed this
missing piece in our deployment process.
The main difficulty here probably lies in the fact that the master and the
regionservers are all unreachable during maintenance. Therefore, there needs to
be some other server to connect to in order to find out the cluster state. This
server could even be shared across multiple clusters, thus unifying a piece of
operational infrastructure that any company running multiple HBase clusters has
to implement. Alternatively, this could be ZK-based, but the ZK instance has to
be different from the one started and stopped with the HBase cluster.
Please share your design ideas.
> 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
