[
https://issues.apache.org/jira/browse/TEZ-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556479#comment-14556479
]
Siddharth Seth commented on TEZ-2450:
-------------------------------------
bq. httpAsyncClient is already marked as volatile. Is there an issue?
Sorry. Missed that. Should be fine.
bq. Calling get() after cancel() (to interrupt worker) would throw
CancellationException. Intention was to check if connect() call can be
interrupted.
This could be achieved by tracking the thread and interrupting it explicitly.
IAC, it'd be good to verify the exception - which can be tracked in the Worker.
future.cancel(true) does send in an Interrupt.
On the Fetcher, should InterruptedException be treated the same as an
IOException - i.e if not shutdown report as failure ? Potentially even throw
the INterruptedException
> support async http clients in ordered & unordered inputs
> --------------------------------------------------------
>
> Key: TEZ-2450
> URL: https://issues.apache.org/jira/browse/TEZ-2450
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Attachments: TEZ-2450.1.patch, TEZ-2450.2.WIP.patch,
> TEZ-2450.2.patch, TEZ-2450.3.patch, TEZ-2450.WIP.patch
>
>
> It will be helpful to switch between JDK & other async http impls. For LLAP
> scenarios, it would be useful to make http clients interruptible which is
> supported in async libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
