[
https://issues.apache.org/jira/browse/PHOENIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652255#comment-16652255
]
Ankit Singhal commented on PHOENIX-4785:
----------------------------------------
bq. There was a deadlock because the HTable threadpool is size 10. All 10 were
being used in for the 10 requests in addRowsInTableDuringRetry(), but when
PhoenixIndexFailurePolicy is triggered, in getTableNoCache for some reason the
same threadpool is used, and there are no more threads available. Changing the
number of threads in the test to 9 instead of 10 fixes this.
just wondering whether this deadlock can also happen in a real cluster having
HBase<1.2 considering the similar configuration? can't we change the threadpool
used by PhoenixIndexFailurePolicy.?
bq. Will commit test fix today unless any objections
Sure you can commit the test and see if above comment makes any sense and
requires a new JIRA.
> 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)
