phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Van Wely (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-3811) Do not disable index on write failure by default
Date Thu, 11 May 2017 18:09:04 GMT

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

Matthew Van Wely edited comment on PHOENIX-3811 at 5/11/17 6:08 PM:
--------------------------------------------------------------------

Thx [~giacomotaylor].  

> If you don't set the REPLAY_AT property and earlier batches are processed before later
batches, you run the risk of overwriting a row with an earlier value

Regarding this, we aim to make all upserts idempotent, by reloading and writing the entire
row, as a retry mechanism to avoid overlapping and out of order writes.  We'll consider if
"replay_at" is still needed.  Thx.


was (Author: mvanwely@gmail.com):
Thx [~giacomotaylor].  

> If you don't set the REPLAY_AT property and earlier batches are processed before later
batches, you run the risk of overwriting a row with an earlier value

Regarding this, we aim to make all upserts idempotents by reloading and writing the entire
row, as a retry mechanism to avoid overlapping and out of order writes.  We'll consider if
"replay_at" is still needed.  Thx.

> 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