[
https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514643#comment-16514643
]
Vincent Poon commented on PHOENIX-4785:
---------------------------------------
>And , another thing we should not let the index usable for queries(writes are
>ok) when it is in PENDING_DISABLE state to avoid inconsistency issues even if
>it is for a small time.
The point of having PENDING_DISABLE is to allow queries to still use the index.
Otherwise we could just disable the index on the server side. We need a
period of time to allow the client to retry before we stop using the index. We
have not ack’d a successful write back to the client yet, so from that
perspective it’s still consistent. Even before PHOENIX-4130, there was a
period of inconsistency while the index write failures were retried on the
server side.
> 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)
