[
https://issues.apache.org/jira/browse/HDFS-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174155#comment-14174155
]
Yongjun Zhang commented on HDFS-7221:
-------------------------------------
HI [~clamb],
I think I found the root cause here. With HDFS-7128 fix, the
"dfs.namenode.replication.max-streams-hard-limit" property is better enforced.
And this caused the testFencingStress() test failure reported here, because the
test is a stress one.
I added one line of change to see the test consistently passing:
{code}
harness.conf.setInt(
DFSConfigKeys.DFS_NAMENODE_REPLICATION_STREAMS_HARD_LIMIT_KEY, 16);
{code}
Thanks [~mingma] for fixing HDFS-7128, and [~kihwal], [~cnauroth] for the
discussion there.
I was thinking about whether the soft and hard setting of this property is
ideal, and I noticed that you guys had some discussion there. It sounds that
this property can be even set per node basis based on the hardware a node is
equipped with. But this may complicate the software. I guess for now we just
need to kind in mind that we have this property enforced.
Thanks Charles again for reporting this long outstanding failure of recent
jenkins jobs.
> TestDNFencingWithReplication fails consistently
> -----------------------------------------------
>
> Key: HDFS-7221
> URL: https://issues.apache.org/jira/browse/HDFS-7221
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.6.0
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Priority: Minor
> Attachments: HDFS-7221.001.patch, HDFS-7221.002.patch
>
>
> TestDNFencingWithReplication consistently fails with a timeout, both in
> jenkins runs and on my local machine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
