<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Concern about Replication when Scheduled NameNode Maintenance in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Concern-about-Replication-when-Scheduled-NameNode/m-p/45942#M42746</link>
    <description>For (1), the answer right now is no. Once the dead node detection occurs, NameNode will swiftly act at re-replicating the identified lost replicas. There's something along the lines of what you need being worked upon upstream via &lt;A href="https://issues.apache.org/jira/browse/HDFS-7877" target="_blank"&gt;https://issues.apache.org/jira/browse/HDFS-7877&lt;/A&gt; but the work is still in progress and will only arrive in a future undetermined CDH release.&lt;BR /&gt;&lt;BR /&gt;For (2), you can hunt such files with replication factor of 1 and raise them to 2 and wait for under-replication count to reach 0 before you take the DN down. The change of replication factor is doable by the command 'hadoop fs -setrep'.</description>
    <pubDate>Wed, 05 Oct 2016 07:43:29 GMT</pubDate>
    <dc:creator>Harsh J</dc:creator>
    <dc:date>2016-10-05T07:43:29Z</dc:date>
    <item>
      <title>Concern about Replication when Scheduled NameNode Maintenance</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Concern-about-Replication-when-Scheduled-NameNode/m-p/45941#M42745</link>
      <description>&lt;P&gt;CentOS 6.6&lt;BR /&gt;CDH 5.1.2&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I would like to take down a DataNode temporary (say, for 24 hours). Some questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;For normally replicated blocks (target replication factor=3), can I disable HDFS to automatically re-replicate those blocks?&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;For&amp;nbsp;un-replicated blocks (replication factor=1), can I do anything to pre-relocate those blocks in case they are in the DataNode to be taken down?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Understand I risk data loss. But those were not critical data anyway.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2016 06:58:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Concern-about-Replication-when-Scheduled-NameNode/m-p/45941#M42745</guid>
      <dc:creator>athtsang</dc:creator>
      <dc:date>2016-10-05T06:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Concern about Replication when Scheduled NameNode Maintenance</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Concern-about-Replication-when-Scheduled-NameNode/m-p/45942#M42746</link>
      <description>For (1), the answer right now is no. Once the dead node detection occurs, NameNode will swiftly act at re-replicating the identified lost replicas. There's something along the lines of what you need being worked upon upstream via &lt;A href="https://issues.apache.org/jira/browse/HDFS-7877" target="_blank"&gt;https://issues.apache.org/jira/browse/HDFS-7877&lt;/A&gt; but the work is still in progress and will only arrive in a future undetermined CDH release.&lt;BR /&gt;&lt;BR /&gt;For (2), you can hunt such files with replication factor of 1 and raise them to 2 and wait for under-replication count to reach 0 before you take the DN down. The change of replication factor is doable by the command 'hadoop fs -setrep'.</description>
      <pubDate>Wed, 05 Oct 2016 07:43:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Concern-about-Replication-when-Scheduled-NameNode/m-p/45942#M42746</guid>
      <dc:creator>Harsh J</dc:creator>
      <dc:date>2016-10-05T07:43:29Z</dc:date>
    </item>
  </channel>
</rss>

