[
https://issues.apache.org/jira/browse/HADOOP-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876322#action_12876322
]
sam rash commented on HADOOP-6762:
----------------------------------
Actually, this might be an artifact of the test. The threads in the executor's
threadpool will be interrupted on shutdown. the test doesn't wait for all of
the threads to terminate gracefully before doing so. This means there is a
race in the test for rpc threads to finish before getting interrupted. I have
an updated test that uses a latch to wait for all threads to terminate before
letting the test complete. I haven't been able to repro, but can post the patch
this afternoon and let you try.
please do still post what exception and any relevant looking log parts here.
it will help me ascertain if this is the case
> 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
>
>
> 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.
