[
https://issues.apache.org/jira/browse/HBASE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246568#comment-13246568
]
Nicolas Spiegelberg commented on HBASE-5359:
--------------------------------------------
@Ted: note that setPersist() just means that we have past the conditional
variable of needing to set persistence. In the exception case, we don't need
to set persistence, we just need to let the other thread finish. One
additional feature that we can add is the ability to propagate the exception in
the ExecutorService thread to the RPC thread so the user visibly sees that his
operation has failed.
> Alter in the shell can be too quick and return before the table is altered
> --------------------------------------------------------------------------
>
> Key: HBASE-5359
> URL: https://issues.apache.org/jira/browse/HBASE-5359
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Fix For: 0.96.0
>
> Attachments: HBASE-5359.patch
>
>
> This seems to be a recent change in behavior but I'm still not sure where
> it's coming from.
> The shell is able to call HMaster.getAlterStatus before the TableEventHandler
> is able call AM.setRegionsToReopen so that the returned status shows no
> pending regions. It means that the alter seems "instantaneous" although it's
> far from completed.
--
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
