[
https://issues.apache.org/jira/browse/HDFS-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-3256:
---------------------------------
Attachment: HDFS-3256.patch
Thanks a lot for the review, Todd. Here's an updated patch which adds the
requested log message. The relevant difference since the last patch is just:
{code}
+ String message = "DN " + node + " joining cluster has expanded a
formerly " +
+ "single-rack cluster to be multi-rack. ";
+ if (namesystem.isPopulatingReplQueues()) {
+ message += "Re-checking all blocks for replication, since they should
" +
+ "now be replicated cross-rack";
+ } else {
+ message += "Not checking for mis-replicated blocks because this NN is
" +
+ "not yet processing processing repl queues.";
+ }
+ LOG.info(message);
{code}
> HDFS considers blocks under-replicated if topology script is configured with
> only 1 rack
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-3256
> URL: https://issues.apache.org/jira/browse/HDFS-3256
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-3256.patch, HDFS-3256.patch, HDFS-3256.patch,
> HDFS-3256.patch, HDFS-3256.patch
>
>
> HDFS treats the mere presence of a topology script being configured as
> evidence that there are multiple racks. If there is in fact only a single
> rack, the NN will try to place the blocks on at least two racks, and thus
> blocks will be considered to be under-replicated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
