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-950) Improve Secondary Index Update Failure Handling
Date Sun, 29 Jun 2014 10:43:24 GMT

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

James Taylor commented on PHOENIX-950:
--------------------------------------

+1 on your plan. How about we start with a patch for the short-term workaround?

> Improve Secondary Index Update Failure Handling
> -----------------------------------------------
>
>                 Key: PHOENIX-950
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-950
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>         Attachments: Improve Phoenix Secondary Index Update Failure Handling.pdf, TransactionSupportPhoenixSecondaryIndexUpdate.pdf
>
>
> Current secondary index update could trigger chained region server failures. This isn't
friendly to end-users. Even we disable index after index update failures before aborting,
it will involve lot of human involvement because index update failure isn't a rare situation.
> In this JIRA, I propose a 2PC like protocol. The "like" means it's a not a real 2PC because
no infinitely blocking but it requires read time(query) to reconcile inconsistence between
index and data. Since I'm not familiar with the query time logic, please let me know if the
proposal could fly.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message