[
https://issues.apache.org/jira/browse/HDFS-14135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833734#comment-16833734
]
Masatake Iwasaki commented on HDFS-14135:
-----------------------------------------
I got the same error on HDFS-14466. The cause seems to be race between
{{consumeConnectionBacklog}} and tests as discussed here.
I guess that the reason why ServerSocket is used for "connect timed out" tests
is to make sure the port is not accidentally listened by other tests or
something. How about using [reserved
address|https://en.wikipedia.org/wiki/Reserved_IP_addresses] like 192.0.2.1 as
a target NN address rather than localhost? We don't need fill TCP backlog if
the target address is always times out on connecting.
The "read timed out" tests still need ServerSocket and I think there is no
timing issue.
> TestWebHdfsTimeouts Fails intermittently in trunk
> -------------------------------------------------
>
> Key: HDFS-14135
> URL: https://issues.apache.org/jira/browse/HDFS-14135
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: HDFS-14135-01.patch, HDFS-14135-02.patch,
> HDFS-14135-03.patch, HDFS-14135-04.patch, HDFS-14135-05.patch,
> HDFS-14135-06.patch, HDFS-14135-07.patch, HDFS-14135-08.patch
>
>
> Reference to failure
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/982/testReport/junit/org.apache.hadoop.hdfs.web/TestWebHdfsTimeouts/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
