[
https://issues.apache.org/jira/browse/PHOENIX-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969573#comment-15969573
]
Andrew Purtell edited comment on PHOENIX-3789 at 4/14/17 9:49 PM:
------------------------------------------------------------------
[~giacomotaylor] [~gjacoby] Wouldn't it be fair to say if there is an index
defined on a Phoenix table then the durability hint of SKIP_WAL can just be
ignored? The Durability thing is just a hint anyway, that WAL entries are not
_required_. Well, if there are indexes, we could require them nonetheless.
Something to think about.
was (Author: apurtell):
[~giacomotaylor] [~gjacoby] Wouldn't it be fair to say if there is an index
defined on a Phoenix table then a mutation with durability of SKIP_WAL can just
be ignored? The Durability thing is just a hint anyway, that WAL entries are
not _required_. Well, if there are indexes, we could require them nonetheless.
Something to think about.
> Execute cross region index maintenance calls outside of row lock
> ----------------------------------------------------------------
>
> 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, 4.10.1
>
> 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)
