[
https://issues.apache.org/jira/browse/HADOOP-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-6762:
--------------------------------
Attachment: hadoop-6762.txt
Rebased on trunk. A few changes since the earlier revs:
- added a new "simple" test case with a single thread
- moved the serialization of the call response into the calling thread, outside
of the lock acquisition, to get better CPU parallelism
- used guava's ThreadFactoryBuilder to make the thread factory
- Cleaned up some of the warning messages to include thread name
> 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: Todd Lipcon
> Priority: Critical
> Fix For: 0.22.0, 0.23.0
>
> Attachments: hadoop-6762-1.txt, hadoop-6762-10.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, hadoop-6762.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
