[ https://issues.apache.org/jira/browse/HDFS-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820649#comment-13820649 ]
Hadoop QA commented on HDFS-5366: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12613454/HDFS-5366.005.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified test files. {color:red}-1 javac{color:red}. The patch appears to cause the build to fail. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5405//console This message is automatically generated. > recaching improvements > ---------------------- > > Key: HDFS-5366 > URL: https://issues.apache.org/jira/browse/HDFS-5366 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: namenode > Affects Versions: 3.0.0 > Reporter: Colin Patrick McCabe > Assignee: Colin Patrick McCabe > Attachments: HDFS-5366-caching.001.patch, HDFS-5366.002.patch, > HDFS-5366.005.patch > > > There are a few things about our HDFS-4949 recaching strategy that could be > improved. > * We should monitor the DN's maximum and current mlock'ed memory consumption > levels, so that we don't ask the DN to do stuff it can't. > * We should not try to initiate caching on stale or decomissioning DataNodes > (although we should not recache things stored on such nodes until they're > declared dead). > * We might want to resend the {{DNA_CACHE}} or {{DNA_UNCACHE}} command a few > times before giving up. Currently, we only send it once. -- This message was sent by Atlassian JIRA (v6.1#6144)