[ https://issues.apache.org/jira/browse/HDFS-7603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298479#comment-14298479 ]
Hudson commented on HDFS-7603: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk #823 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/823/]) HDFS-7603. The background replication queue initialization may not let others run. Contributed by Kihwal Lee. (kihwal: rev 89b07490f8354bb83a67b7ffc917bfe99708e615) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java > The background replication queue initialization may not let others run > ---------------------------------------------------------------------- > > Key: HDFS-7603 > URL: https://issues.apache.org/jira/browse/HDFS-7603 > Project: Hadoop HDFS > Issue Type: Bug > Components: rolling upgrades > Reporter: Kihwal Lee > Assignee: Kihwal Lee > Priority: Critical > Fix For: 2.7.0 > > Attachments: HDFS-7603.patch, HDFS-7603.patch > > > The background replication queue initialization processes configured number > of blocks at a time and releases the namesystem write lock. This was to let > namenode start serving right after a standby to active transition or leaving > safe mode. However, this does not allow others to run much if the lock > fairness is set to "unfair" for the higher throughput. > I propose adding a delay between unlocking and locking in the async repl > queue init thread. -- This message was sent by Atlassian JIRA (v6.3.4#6332)