<?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 How to reset “Reserved Space for Replicas” without restart Hadoop services in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297007#M218544</link>
    <description>&lt;P&gt;How to find why "Reserved Space for Replicas" constantly increasing and &lt;STRONG&gt;how to control/set a space size allocated for the "Reserved Space for Replicas" in Hadoop?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We found that the "Reserved Space for Replicas" not relate to "Non DFS" space and it can increase constantly up to rebooting Data Node-s. We didn't find &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; how to limit space allocated for the "Reserved Space for Replicas" &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We thought that dfs.datanode.du.reserved can control "Reserved Space for Replicas" but it is not!&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jun 2020 19:10:31 GMT</pubDate>
    <dc:creator>Zholaman</dc:creator>
    <dc:date>2020-06-01T19:10:31Z</dc:date>
    <item>
      <title>How to reset “Reserved Space for Replicas” without restart Hadoop services</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297007#M218544</link>
      <description>&lt;P&gt;How to find why "Reserved Space for Replicas" constantly increasing and &lt;STRONG&gt;how to control/set a space size allocated for the "Reserved Space for Replicas" in Hadoop?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We found that the "Reserved Space for Replicas" not relate to "Non DFS" space and it can increase constantly up to rebooting Data Node-s. We didn't find &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; how to limit space allocated for the "Reserved Space for Replicas" &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We thought that dfs.datanode.du.reserved can control "Reserved Space for Replicas" but it is not!&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2020 19:10:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297007#M218544</guid>
      <dc:creator>Zholaman</dc:creator>
      <dc:date>2020-06-01T19:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to reset “Reserved Space for Replicas” without restart Hadoop services</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297057#M218573</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We found that the "Reserved Space for Replicas" &lt;FONT color="#FF0000"&gt;&lt;STRIKE&gt;not&lt;/STRIKE&gt;&lt;/FONT&gt; relate to "Non DFS" space&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jun 2020 05:21:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297057#M218573</guid>
      <dc:creator>Zholaman</dc:creator>
      <dc:date>2020-06-02T05:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to reset “Reserved Space for Replicas” without restart Hadoop services</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297128#M218608</link>
      <description>&lt;P&gt;For people who faced with that type of problem. First of all you should understand the nature of the problem. To do that please read the description of the following issues:&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/HDFS-8072" target="_blank" rel="noopener"&gt;https://issues.apache.org/jira/browse/HDFS-8072&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/browse/HDFS-9530" target="_blank" rel="noopener"&gt;https://issues.apache.org/jira/browse/HDFS-9530&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The following links will be useful to understand what block replica is:&lt;/P&gt;&lt;P&gt;&lt;A href="https://blog.cloudera.com/understanding-hdfs-recovery-processes-part-1/" target="_blank" rel="noopener"&gt;https://blog.cloudera.com/understanding-hdfs-recovery-processes-part-1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://blog.cloudera.com/understanding-hdfs-recovery-processes-part-2/" target="_blank" rel="noopener"&gt;https://blog.cloudera.com/understanding-hdfs-recovery-processes-part-2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Solutions&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Find the wrong software which often broke connection with Hadoop during the write or append processes&lt;/P&gt;&lt;P&gt;2. Try to change replication policy (risky)&lt;/P&gt;&lt;P&gt;3. Update Hadoop up to late version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;You can't reset&amp;nbsp;“Reserved Space for Replicas” without restart Hadoop services!&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 05:29:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-to-reset-Reserved-Space-for-Replicas-without-restart/m-p/297128#M218608</guid>
      <dc:creator>Zholaman</dc:creator>
      <dc:date>2020-06-03T05:29:02Z</dc:date>
    </item>
  </channel>
</rss>

