You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/12 19:02:00 UTC

[jira] [Updated] (HBASE-20178) [AMv2] Throw exception if hostile environment

     [ https://issues.apache.org/jira/browse/HBASE-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-20178:
--------------------------
    Description: 
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.

  was:
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.


> [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
>            Priority: Major
>
> 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)