phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3811) Do not disable index on write failure by default
Date Sat, 13 May 2017 03:01:04 GMT


Lars Hofhansl commented on PHOENIX-3811:

The patch leaves the default in place, no? I.e. the index is disabled as a result of a failed
write, right? (The title says otherwise)

> Do not disable index on write failure by default
> ------------------------------------------------
>                 Key: PHOENIX-3811
>                 URL:
>             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

View raw message