[ https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514248#comment-16514248 ]
Ankit Singhal edited comment on PHOENIX-4785 at 6/15/18 10:02 PM: ------------------------------------------------------------------ [~vincentpoon], we can't simply reset the disabled timestamp as another client may fail in writing during the same time. Shouldn't we DISABLE the index if we find the current state as PENDING_DISABLE when other client fail to write the index? And one more thing why we are allowing a user to use an index in a PENDING_DISABLE state? was (Author: an...@apache.org): [~vincentpoon], we can't simply reset the disabled timestamp as another client may fail in writing during the same time. Shouldn't we DISABLE the index if we find the current state as PENDING_DISABLE when other client fail to write the index? > 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)