[
https://issues.apache.org/jira/browse/PHOENIX-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080463#comment-14080463
]
Hudson commented on PHOENIX-950:
--------------------------------
SUCCESS: Integrated in Phoenix | Master | Hadoop1 #312 (See
[https://builds.apache.org/job/Phoenix-master-hadoop1/312/])
Phoenix-950: Improve Secondary Index Update Failure Handling - addendum
(jeffreyz: rev a8113ac0def2ef7d76af35afab509dc6ce6b624d)
* pom.xml
> 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)
