[
https://issues.apache.org/jira/browse/HDFS-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896242#comment-13896242
]
Hadoop QA commented on HDFS-5917:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12627914/HDFS-5917.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6091//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6091//console
This message is automatically generated.
> Have an ability to refresh deadNodes list periodically
> ------------------------------------------------------
>
> Key: HDFS-5917
> URL: https://issues.apache.org/jira/browse/HDFS-5917
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Attachments: HDFS-5917.txt
>
>
> In current HBase + HDFS trunk impl, if one node is inserted into deadNodes
> list, before deadNodes.clear() be invoked, this node could not be choose
> always. When i fixed HDFS-5637, i had a raw thought, since there're not a few
> conditions could trigger a node be inserted into deadNodes, we should have
> an ability to refresh this important cache list info automaticly. It's
> benefit for HBase scenario at least, e.g. before HDFS-5637 fixed, if a local
> node be inserted into deadNodes, then it will read remotely even the local
> node is not dead:) if more unfortunately, this block is in a huge HFile which
> doesn't be picked into any minor compaction in short period, the performance
> penality will be continued until a large compaction or region reopend or
> deadNodes.clear() be invoked...
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
