[
https://issues.apache.org/jira/browse/PHOENIX-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971609#comment-15971609
]
James Taylor commented on PHOENIX-3789:
---------------------------------------
bq. Can we implement both hooks in Phoenix and then determine within the hook
whether this is a local index or not?
I don't mean a local index. These are all global indexes. I'm saying that if we
have a batch of 200 index updates, some of them will happen to be associated
with regions of the index table that are local to the region server. In theory,
we could only process that subset in the postBatchMutate and process the others
in the postBatchMutateIndispensably. This is going to be a bigger change than
we want to make right now IMHO.
> Execute cross region index maintenance calls in postBatchMutateIndispensably
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-3789
> URL: https://issues.apache.org/jira/browse/PHOENIX-3789
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.11.0
>
> Attachments: PHOENIX-3789.patch, PHOENIX-3789_v2.patch
>
>
> Making cross region server calls while the row is locked can lead to a
> greater chance of resource starvation. We can use the
> postBatchMutateIndispensably hook instead of the postBatchMutate call for our
> processing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
