[
https://issues.apache.org/jira/browse/HBASE-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208413#comment-14208413
]
Andrew Purtell commented on HBASE-12433:
----------------------------------------
bq. In the BulkReopen, this method directly returns true without any waiting.
Until the region is reopened, the order won't be changed.
Is that the issue though? We just need to, eventually, when the region is
reopened to apply the schema update, have the coprocessor ordering change
apply. I don't think James is reporting the changes have to be applied before
the admin call returns. I think he's reporting that time goes by and the
changes never seem to be applied.
When the region is reopened, is the schema change available at that time?
Are the coprocessors on the region being reloaded?
> Coprocessors not dynamically reordered when reset priority
> ----------------------------------------------------------
>
> Key: HBASE-12433
> URL: https://issues.apache.org/jira/browse/HBASE-12433
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Affects Versions: 0.98.7
> Reporter: James Taylor
>
> When modifying the coprocessor priority through the HBase shell, the order of
> the firing of the coprocessors wasn't changing. It probably would have with a
> cluster bounce, but if we can make it dynamic easily, that would be
> preferable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
