[ https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515224#comment-16515224 ]
Ankit Singhal edited comment on PHOENIX-4785 at 6/17/18 9:13 PM: ----------------------------------------------------------------- Uploaded a v2 patch, which we will check the counter for the clients working on PENDING_DISABLE state before enabling the index. Current testcase doesn't reproduce the issue with multiple clients , trying to test it on the cluster. was (Author: an...@apache.org): Uploaded a v2 patch, which we will check the counter for the clients working on PENDING_DISABLE state before enabling 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, > PHOENIX-4785_v2.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)