[
https://issues.apache.org/jira/browse/PHOENIX-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666877#comment-16666877
]
Abhishek Singh Chouhan commented on PHOENIX-4990:
-------------------------------------------------
I think we might also cause delays in region closing/splitting if we wait
during the time of coproc shutdown. Since we shutdown the coproc only after
updates are disabled for region we could have times of unavailability upto the
specified value.
>I think the original issue I was trying to fix was actually caused by
>PHOENIX-4993
+1. Ideally we should not end up in a situation where index writes are still
happening while we come to the point of coproc being shutdown, since all writes
+ index updates should've already completed by then. Wdyt [~vincentpoon]?
> 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)
