[
https://issues.apache.org/jira/browse/HDFS-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660173#comment-13660173
]
Colin Patrick McCabe commented on HDFS-4824:
--------------------------------------------
Looks like someone or something deleted the socket directory in /tmp that
{{TestShortCircuitLocalRead}} was using.
{code}
Tests in error:
testFileLocalReadNoChecksum(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.35104.sock'
testFileLocalReadChecksum(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.56667.sock'
testSmallFileLocalRead(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.47030.sock'
testLocalReadLegacy(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.50662.sock'
testLocalReadFallback(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.34831.sock'
testReadFromAnOffset(org.apache.hadoop.hdfs.TestShortCircuitLocalRead):
bind(2) error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.47719.sock'
testLongFile(org.apache.hadoop.hdfs.TestShortCircuitLocalRead): bind(2)
error: No such file or directory when trying to bind to
'/tmp/socks.1368743681542.2028583750/TestShortCircuitLocalRead.58149.sock'
{code}
I've never seen this one before, and it definitely doesn't reproduce here.
Rogue /tmp cleaner process? I guess let's re-run.
> FileInputStreamCache.close leaves dangling reference to
> FileInputStreamCache.cacheCleaner
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-4824
> URL: https://issues.apache.org/jira/browse/HDFS-4824
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.0.4-alpha
> Reporter: Henry Robinson
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-4824.001.patch, HDFS-4824.002.patch
>
>
> {{FileInputStreamCache}} leaves around a reference to its {{cacheCleaner}}
> after {{close()}}.
> The {{cacheCleaner}} is created like this:
> {code}
> if (cacheCleaner == null) {
> cacheCleaner = new CacheCleaner();
> executor.scheduleAtFixedRate(cacheCleaner, expiryTimeMs,
> expiryTimeMs,
> TimeUnit.MILLISECONDS);
> }
> {code}
> and supposedly removed like this:
> {code}
> if (cacheCleaner != null) {
> executor.remove(cacheCleaner);
> }
> {code}
> However, {{ScheduledThreadPoolExecutor.remove}} returns a success boolean
> which should be checked. And I _think_ from a quick read of that class that
> the return value of {{scheduleAtFixedRate}} should be used as the argument to
> {{remove}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
