[
https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514536#comment-16514536
]
Vincent Poon commented on PHOENIX-4785:
---------------------------------------
[~an...@apache.org] Yes, that's a shortcoming - I don't have any good idea to
get around that. We are trying to strike a balance between not being overly
aggressive in disabling the index, and still have the index be as consistent as
possible. It's difficult to have both. I think the case of two clients both
concurrently writing AND one succeeds and the other fails AND one goes away ,
is a case we have to compromise on for the time being. Open to suggestions on
this.
> Unable to write to table if index is made active during retry
> -------------------------------------------------------------
>
> Key: PHOENIX-4785
> URL: https://issues.apache.org/jira/browse/PHOENIX-4785
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Romil Choksi
> Assignee: Vincent Poon
> Priority: Blocker
> Fix For: 5.0.0, 4.14.1
>
> Attachments: PHOENIX-4785.v1.master.patch, PHOENIX-4785_test.patch
>
>
> After PHOENIX-4130, we are unable to write to a table if an index is made
> ACTIVE during the retry as client timestamp is not cleared when table state
> is changed from PENDING_DISABLE to ACTIVE even if our policy is not to block
> writes on data table in case of write failure for index.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
