hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10468) HDFS read ends up ignoring an interrupt
Date Fri, 27 May 2016 21:42:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304851#comment-15304851

Jing Zhao commented on HDFS-10468:

When the {{blockSeekTo}} gets {{ClosedByInterruptException}}, the IO channels have already
been interrupted. Instead of retrying the read with other DataNodes for reading, maybe a better
choice here is to check the current thread's interrupt state and throw the {{ClosedByInterruptException}}
to upper level. Will upload a patch for this. 

> 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: 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message