<?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: HDFS Federation understanding in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDFS-Federation-understanding/m-p/33911#M10250</link>
    <description>Your understanding seems right, but note that none of the 'splitting' is automatic.&lt;BR /&gt;&lt;BR /&gt;At its simplest form, federation is a way to have multiple distinct NameNodes powered by a common set of DataNodes.&lt;BR /&gt;&lt;BR /&gt;Effectively, its running and managing 2 or more *separate* namespaces on top of the same storage space.&lt;BR /&gt;&lt;BR /&gt;If you deploy two federated NameNodes, say hdfs://host-nn1/ and hdfs://host-nn2, then they will have nothing in common except the Live DN hostnames they share. A 'hadoop fs -ls' done on each will return absolutely independent results.</description>
    <pubDate>Sun, 08 Nov 2015 15:27:57 GMT</pubDate>
    <dc:creator>Harsh J</dc:creator>
    <dc:date>2015-11-08T15:27:57Z</dc:date>
    <item>
      <title>HDFS Federation understanding</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDFS-Federation-understanding/m-p/33907#M10249</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just tring to understand better the HDFS Federation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I get it right:&lt;/P&gt;&lt;P&gt;- we should use it in order to split for example the&amp;nbsp;real time space and the batch space.&lt;/P&gt;&lt;P&gt;- if we want to split the namespace into N namespaces than we have to have N namenodes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alina&lt;/P&gt;</description>
      <pubDate>Sun, 08 Nov 2015 15:03:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDFS-Federation-understanding/m-p/33907#M10249</guid>
      <dc:creator>AlinaGHERMAN</dc:creator>
      <dc:date>2015-11-08T15:03:41Z</dc:date>
    </item>
    <item>
      <title>Re: HDFS Federation understanding</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDFS-Federation-understanding/m-p/33911#M10250</link>
      <description>Your understanding seems right, but note that none of the 'splitting' is automatic.&lt;BR /&gt;&lt;BR /&gt;At its simplest form, federation is a way to have multiple distinct NameNodes powered by a common set of DataNodes.&lt;BR /&gt;&lt;BR /&gt;Effectively, its running and managing 2 or more *separate* namespaces on top of the same storage space.&lt;BR /&gt;&lt;BR /&gt;If you deploy two federated NameNodes, say hdfs://host-nn1/ and hdfs://host-nn2, then they will have nothing in common except the Live DN hostnames they share. A 'hadoop fs -ls' done on each will return absolutely independent results.</description>
      <pubDate>Sun, 08 Nov 2015 15:27:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDFS-Federation-understanding/m-p/33911#M10250</guid>
      <dc:creator>Harsh J</dc:creator>
      <dc:date>2015-11-08T15:27:57Z</dc:date>
    </item>
  </channel>
</rss>

