[
https://issues.apache.org/jira/browse/HDFS-14135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714236#comment-16714236
]
Ayush Saxena commented on HDFS-14135:
-------------------------------------
[~elgoiri] For the testTwoStepWriteConnectTimeout() I thought that it is a race
between the main thread and the startSingleTemporaryRedirectResponseThread().
Before the latter sets the platform the main is getting executed.That is why
there is no failure.But I don't think that this is actually the problem.I guess
there is some problem with the method consumeConnectionBacklog().This doesn't
seem to work as intended at the Jenkins side.As almost tests dependent on it
are failing.This issue has been earlier taken up too in HDFS-11043.Catching up
the discussion there.There suspect was also on CLIENTS_TO_CONSUME_BACKLOG. But
I guess then value set wasn't that the yetus expects or it got changed
latter.If somehow we mange to get
/proc/sys/net/ipv4/tcp_max_syn_backlog from the there and set the same value
here.I guess this might get solved.
> 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
>
>
> 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
