[
https://issues.apache.org/jira/browse/HBASE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629223#action_12629223
]
stack commented on HBASE-678:
-----------------------------
Yeah, Billy, as you suggest elsewhere, compaction should not be inline with
close.
In above, you are suggesting that when in 'safe mode', no compactions or splits
so balancing happens promptly?
On exit of 'safe mode', the compactions and splits could begin?
I suppose the master can send a message to all regionservers when it wants all
to leave 'safe mode'.
> hbase needs a 'safe-mode'
> -------------------------
>
> Key: HBASE-678
> URL: https://issues.apache.org/jira/browse/HBASE-678
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.19.0
>
>
> Internally we have a cluster of thousands of regions. We just did a hbase
> restart w/ master on new node. Just so happened that one of the
> regionservers was running extra slow (was downloaded by other processes).
> Meant that its portion of the assigments was taking a long time to come up...
> While these regions were stuck in deploy mode, the cluster is not useable.
> We need a sort of 'safe-mode' in hbase where clients fail if they try to
> attach to a cluster not yet fully up. UI should show when all assignments
> have been successfully made so admin can at least see when they have a
> problematic regionserver in their midst.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
