[
https://issues.apache.org/jira/browse/HDFS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309398#comment-15309398
]
Masatake Iwasaki commented on HDFS-10468:
-----------------------------------------
{code}
678 DFSClient.LOG.warn("The reading thread has been interrupted:
{}.", ex);
{code}
nit: "{}" was not replaced since the second argument is Exception.
{noformat}
2016-06-01 14:10:29,476 [Thread-95] WARN hdfs.DFSClient
(DFSInputStream.java:blockSeekTo(678)) - The reading thread has been
interrupted: {}.
java.nio.channels.ClosedByInterruptException
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
...
{noformat}
> HDFS read ends up ignoring an interrupt
> ---------------------------------------
>
> Key: HDFS-10468
> URL: https://issues.apache.org/jira/browse/HDFS-10468
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Jing Zhao
> Attachments: HDFS-10468.000.patch, HDFS-10468.001.patch, log
>
>
> If an interrupt comes in during an HDFS read - it looks like HDFS ends up
> ignoring it (handling it), and retries the read after an interval.
> An interrupt should result in the read being cancelled, with an
> InterruptedException being thrown.
> Similarly - if an HDFS op is started with the interrupt status on the thread
> set, an InterruptedException should be thrown.
> cc [~jingzhao]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
