[
https://issues.apache.org/jira/browse/HBASE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629240#action_12629240
]
Billy Pearson commented on HBASE-678:
-------------------------------------
yes that's what I was thanking we could still queue up the compaction request
on the region server but only start the compactions once the master leaves safe
mode.
Let the master send the message to the region server or let the region server
query the master for safe mode status.
If we do not want to stop compaction while in safe mode then we need to decline
to close a region for redeployment while there is a compaction happening.
> 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.
