[
https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652577#comment-16652577
]
Vincent Poon commented on PHOENIX-4785:
---------------------------------------
[[email protected]] I think this is mostly a test-only issue. What's happening
is we use DriverManager#createConnection on both client and server side in the
test. This ends up using the same HConnection because our test client and
server are in the same JVM. So this shouldn't happen in a real cluster, though
there might be some weird edge case that could trigger this. I created
PHOENIX-4978 to track it.
> 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: Ankit Singhal
> Priority: Blocker
> Fix For: 5.0.0, 4.14.1
>
> Attachments: PHOENIX-4785.addendum.HBase-1.2.patch,
> PHOENIX-4785.v1.master.patch, PHOENIX-4785_test.patch, PHOENIX-4785_v2.patch,
> PHOENIX-4785_v2_5.0-branch.patch, PHOENIX-4785_v3_master.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)
