phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3811) Do not disable index on write failure by default
Date Fri, 12 May 2017 01:18:04 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007468#comment-16007468
] 

James Taylor commented on PHOENIX-3811:
---------------------------------------

Thanks for the review, [~tdsilva]. I've pushed to master and 4.x branches. I had to disable
MutableIndexFailureIT for 4.x-HBase-1.1 and 4.x-HBase-0.98 branches as we were seeing test
failures due to row lock issues. I've filed PHOENIX-3848 for follow up work.

> Do not disable index on write failure by default
> ------------------------------------------------
>
>                 Key: PHOENIX-3811
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3811
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3811_v1.patch, PHOENIX-3811_v2.patch, PHOENIX-3811_v3.patch,
PHOENIX-3811-wip1.patch, PHOENIX-3811-wip2.patch, PHOENIX-3811-wip3.patch, PHOENIX-3811-wip4.patch,
PHOENIX-3811-wip5.patch, PHOENIX-3811-wip7.patch
>
>
> We should provide a way to configure the system so that the server takes no specific
action when an index write fails. Since we always throw the write failure back to the client,
the client can often deal with failures more easily than the server since they have the batch
of mutations in memory. Often times, allowing access to an index that may be one batch behind
the data table is better than disabling it given the negative performance that will occur
while the index cannot be written to.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message