[
https://issues.apache.org/jira/browse/HBASE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439806#comment-13439806
]
Andrew Purtell commented on HBASE-5320:
---------------------------------------
Doesn't the answer when all of these issues are reduced end at async/callback
based request handling? We've started moving the client this direction
internally. An explicit async API exposed on top a-la asynchbase would let the
client detect unreachability (or some other error) via callback on a per
request basis, this would be the canonical pattern, right?
Then the client can decide, in the error callback, if it would like to reissue
the request. Or not. No need for shared state.
Not an argument to the above, just a question for consideration if it may be
useful.
> 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
