phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4028) Provide option to not throw index write failure back to client
Date Tue, 18 Jul 2017 23:10:00 GMT

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

Samarth Jain commented on PHOENIX-4028:
---------------------------------------

[~jamestaylor], I just realized that there is a problem with this patch. Our rebuild index
job will wrongly mark the index as active even though it possibly wasn't able to write to
the index as part of the rebuild.

> Provide option to not throw index write failure back to client
> --------------------------------------------------------------
>
>                 Key: PHOENIX-4028
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4028
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4028.patch, PHOENIX-4028_v2.patch, PHOENIX-4028_v3.patch,
PHOENIX-4028_v4.patch, PHOENIX-4028_wip.patch
>
>
> Much like our DISABLE_INDEX_ON_WRITE_FAILURE and REBUILD_INDEX_ON_WRITE_FAILURE table
properties, we need a THROW_INDEX_WRITE_FAILURE boolean option that can be used to prevent
the index write from being thrown back to the client. In this case, the index failure policy
would still be executed (i.e. disabling the index on a write failure), but any retry logic
for the client would be avoided. The index would be eventually consistent based on the background
partial index rebuild thread.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message