<?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: Warning: fs.defaultFS is not set in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/78308#M62679</link>
    <description>&lt;P&gt;Whats the resolution?&lt;/P&gt;</description>
    <pubDate>Thu, 09 Aug 2018 15:02:21 GMT</pubDate>
    <dc:creator>SF1</dc:creator>
    <dc:date>2018-08-09T15:02:21Z</dc:date>
    <item>
      <title>Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/55668#M62676</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a 8 node cloudera cluster with three master nodes &amp;nbsp;contains master deamons up and running and three slave nodes contains all slave deamons up and running and two edge nodes to access hadoop services. Hue is installed on both of the edge nodes. It is managed from cloudera manager.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have deployed client configuraion across all nodes. Environement variable is set correctly. Checked hadoop configuration in my edgenodes. But unable to access hadoop services by hdfs fs shell command. Endpoints are configured properly and hue works fine. I can run all hdfs fs shell commands in my master and slave nodes. It is a very basic question. I have checked the possible corners in the server. But I cant locate the problem. Could you please help me get rid of the issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;sudo -u hdfs hadoop fs -ls /
Warning: fs.defaultFS is not set when running "ls" command.
Found 21 items
-rw-r--r--   1 root root          0 2017-06-07 18:31 /.autorelabel
-rw-r--r--   1 root root          0 2017-05-16 19:55 /1
dr-xr-xr-x   - root root      28672 2017-06-10 06:16 /bin
dr-xr-xr-x   - root root       4096 2017-05-16 20:03 /boot
drwxr-xr-x   - root root       3040 2017-06-07 18:31 /dev
drwxr-xr-x   - root root       8192 2017-06-10 07:22 /etc
drwxr-xr-x   - root root         56 2017-06-10 07:22 /home
dr-xr-xr-x   - root root       4096 2017-06-10 06:15 /lib
dr-xr-xr-x   - root root      32768 2017-06-10 06:15 /lib64
drwxr-xr-x   - root root          6 2016-11-05 15:38 /media
drwxr-xr-x   - root root         35 2017-06-07 01:57 /mnt
drwxr-xr-x   - root root         45 2017-06-10 06:14 /opt
dr-xr-xr-x   - root root          0 2017-06-08 11:04 /proc
dr-xr-x---   - root root       4096 2017-06-10 06:23 /root
drwxr-xr-x   - root root        860 2017-06-10 06:16 /run
dr-xr-xr-x   - root root      20480 2017-06-07 19:47 /sbin
drwxr-xr-x   - root root          6 2016-11-05 15:38 /srv
dr-xr-xr-x   - root root          0 2017-06-08 11:04 /sys
drwxrwxrwt   - root root       4096 2017-06-11 10:32 /tmp
drwxr-xr-x   - root root        167 2017-06-07 19:43 /usr
drwxr-xr-x   - root root       4096 2017-06-07 19:46 /var&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;RK.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jun 2017 10:44:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/55668#M62676</guid>
      <dc:creator>rkkrishnaa</dc:creator>
      <dc:date>2017-06-11T10:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/55806#M62677</link>
      <description>&lt;P&gt;Hey rkkrishnaa,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has the edge node been assigned a the "HDFS Gateway" role? You can confirm this by clicking on "Hosts" and expanding the roles.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2017 19:21:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/55806#M62677</guid>
      <dc:creator>Borg</dc:creator>
      <dc:date>2017-06-13T19:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/64637#M62678</link>
      <description>Thank you. It was working fine.</description>
      <pubDate>Thu, 15 Feb 2018 17:39:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/64637#M62678</guid>
      <dc:creator>rkkrishnaa</dc:creator>
      <dc:date>2018-02-15T17:39:03Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/78308#M62679</link>
      <description>&lt;P&gt;Whats the resolution?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 15:02:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/78308#M62679</guid>
      <dc:creator>SF1</dc:creator>
      <dc:date>2018-08-09T15:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/80460#M62680</link>
      <description>&lt;P&gt;Brother&lt;/P&gt;&lt;P&gt;Just go to HDFS --&amp;gt; Instances --&amp;gt; (Then click on) Add role instances --&amp;gt; &amp;amp; just select &amp;amp; configure "Gateway" on a host.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Your problem will be resolved... in-sha-ALLAH.&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Screenshot (77).png" style="width: 600px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/4868i9AA4B9170412C73F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (77).png" alt="Screenshot (77).png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Sep 2018 12:13:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/80460#M62680</guid>
      <dc:creator>BakshiZeeshanAh</dc:creator>
      <dc:date>2018-09-30T12:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Warning: fs.defaultFS is not set</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/93984#M62681</link>
      <description>&lt;P&gt;This can be a case to case incident. In some cases we need to remove and replace the content of the&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;/opt/cloudera/parcels/CDH/lib/hadoop/etc/hadoop&lt;/STRONG&gt; directory from the other nodes of the same cluster if this node is added from some other cluster. This is because the directory may not be cleared before adding the server to the new cluster. The existing files form the old cluster may not work as expected in the new cluster as the parameters in the configuration files may vary from cluster to cluster. So we need to forcefully remove the contents and add them manually.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 07:43:26 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Warning-fs-defaultFS-is-not-set/m-p/93984#M62681</guid>
      <dc:creator>AnuLS</dc:creator>
      <dc:date>2019-08-13T07:43:26Z</dc:date>
    </item>
  </channel>
</rss>

