[
https://issues.apache.org/jira/browse/PHOENIX-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664188#comment-16664188
]
Vincent Poon commented on PHOENIX-4990:
---------------------------------------
[~gjacoby] Attached a v3 that modifies the test to bypass PHOENIX-4992. But
then I ran into other test failures. At this point I'm hesitant to push this
because although it seems like test-related issues only, I'm not 100% certain.
Just going to park this for now, feel free to take this up if you get time.
It's still important to fix this, but I think the original issue I was trying
to fix was actually caused by PHOENIX-4993
> When stopping IndexWriter, give tasks a chance to complete
> ----------------------------------------------------------
>
> Key: PHOENIX-4990
> URL: https://issues.apache.org/jira/browse/PHOENIX-4990
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Vincent Poon
> Assignee: Vincent Poon
> Priority: Major
> Attachments: PHOENIX-4990.v1.4.x-HBase-1.4.patch,
> PHOENIX-4990.v2.4.x-HBase-1.4.patch, PHOENIX-4990.v3.4.x-HBase-1.4.patch
>
>
> We've seen a race condition where an index write failure happens when a
> coprocessor is shutting down. Since we don't give the index writer threads a
> chance to complete when shutdownNow() is called, there is a chance the
> coprocessor shuts down its HTables while an index writer thread is in
> PhoenixIndexFailurePolicy trying to disable an index, which ends up using a
> closed HTable and received RejectedExecutionException
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
