[
https://issues.apache.org/jira/browse/TEZ-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099155#comment-14099155
]
Bikas Saha commented on TEZ-1331:
---------------------------------
Please keep the waitTillReady(). Thats needed until we transparently allow the
prewarm to get superceded by the next real dag.
Approach sounds good to me. Essentially, where the API is explicitly asking the
user to wait then it expects the user to handled interruptions. For other cases
it avoids potentially nagging handling of interrupted exceptions. This follows
most of existing Java standard API code where all the wait methods throw
interrupted but not every API that may be blocking.
Later we can look at setting the Thread's interrupted status upon interruption
so that users can use that to inspect for that condition. Thats another way to
expose the interrupted status. It wont be backwards incompatible.
> Investigate : interrupts being swallowed by TezClient/DAGClient methods
> -----------------------------------------------------------------------
>
> Key: TEZ-1331
> URL: https://issues.apache.org/jira/browse/TEZ-1331
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Priority: Blocker
> Attachments: TEZ-1331.1.patch
>
>
> TEZ-1278 fixes waitTillReady to not ignore interrupts. This jira is to look
> through other APIs to figure out whether interrupts handling needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
