[
https://issues.apache.org/jira/browse/HADOOP-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902685#action_12902685
]
sam rash commented on HADOOP-6762:
----------------------------------
I think IOException makes sense for 2 reasons
1. the reason you stated--we can pass the actual cause
2. my read is that only if you are the thread doing the IO should you throw
InterruptedIOException. In this case, the thread truly was interrupted--the IO
happens in the other thread.
http://download-llnw.oracle.com/javase/6/docs/api/java/io/InterruptedIOException.html
it also has a field for the partial bytes transfered. In fact, this patch is
supposed to keep the IO from actually being interrupted :)
how can we make it so the test will pass? does the test have a faulty
assumption that I should fix?
> exception while doing RPC I/O closes channel
> --------------------------------------------
>
> Key: HADOOP-6762
> URL: https://issues.apache.org/jira/browse/HADOOP-6762
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.20.2
> Reporter: sam rash
> Assignee: sam rash
> Attachments: hadoop-6762-1.txt, hadoop-6762-2.txt, hadoop-6762-3.txt,
> hadoop-6762-4.txt, hadoop-6762-6.txt, hadoop-6762-7.txt, hadoop-6762-8.txt,
> hadoop-6762-9.txt
>
>
> If a single process creates two unique fileSystems to the same NN using
> FileSystem.newInstance(), and one of them issues a close(), the leasechecker
> thread is interrupted. This interrupt races with the rpc namenode.renew()
> and can cause a ClosedByInterruptException. This closes the underlying
> channel and the other filesystem, sharing the connection will get errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
