[
https://issues.apache.org/jira/browse/HBASE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557449#comment-13557449
]
Lars Hofhansl edited comment on HBASE-5359 at 1/18/13 6:31 PM:
---------------------------------------------------------------
yeah I missed this one. Let's backport.
Also, looking at the patch, why are we using waitForPersist/setPersist instead
of just waiting until the future returned from submit indicates that it is done?
was (Author: lhofhansl):
yeah I missed this one. Let's backport.
Also, looking at the patch, why are we using waitForPersist/setPersist instead
of just waiting until the future return from submit indicates that it is done?
> 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
> Assignee: Nicolas Spiegelberg
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
