[
https://issues.apache.org/jira/browse/PHOENIX-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008820#comment-16008820
]
Enis Soztutar commented on PHOENIX-3789:
----------------------------------------
Thanks James, good to know. Agreed that this is way more scalable, but I was
more concerned about the fact that the design for the secondary indexes was
such that the index update will be visible before the data table update. If is
it not a problem in terms of "correctness", then this approach is better.
> 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_addendum1.patch,
> PHOENIX-3789_addendum2.patch, 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)
