[ 
https://issues.apache.org/jira/browse/HBASE-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398071#comment-16398071
 ] 

stack commented on HBASE-20178:
-------------------------------

Failures are good ones. Come mostly of our now failing fast or our making an 
assert that doesn't hold. .006 does fixes.

> [AMv2] Throw exception if hostile environment
> ---------------------------------------------
>
>                 Key: HBASE-20178
>                 URL: https://issues.apache.org/jira/browse/HBASE-20178
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: 
> 0001-HBASE-20178-AMv2-Throw-exception-if-hostile-environm.patch, 
> HBASE-20178.branch-2.001.patch, HBASE-20178.branch-2.002.patch, 
> HBASE-20178.branch-2.003.patch, HBASE-20178.branch-2.004.patch, 
> HBASE-20178.branch-2.005.patch, HBASE-20178.branch-2.006.patch
>
>
> New pattern where we throw exception on procedure construction if cluster is 
> going down, hosting master is stopping, table is offline, or table is 
> read-only. Fail fast rather than later internal to Procedure so can flag 
> caller there is a problem.
> Changed Move/Split/Merge Procedures.
> No point queuing a move region for a table that is offline and which may 
> never be re-enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to