incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-2789) Change core-site.xml's fs.default.name to fs.defaultFS for 2.0 stack deployment
Date Thu, 01 Aug 2013 02:07:48 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako updated AMBARI-2789:
--------------------------------

    Description: 
We need to have only one of the two (fs.default.name or fs.defaultFS, and the former is deprecated).
If both are present then NN HA will be enabled/disabled based on what is read first.

Following is description from NN HA in Apache docs:

fs.defaultFS - the default path prefix used by the Hadoop FS client when none is given.
Optionally, you may now configure the default path for Hadoop clients to use the new HA-enabled
logical URI. If you used "mycluster" as the nameservice ID earlier, this will be the value
of the authority portion of all of your HDFS paths. This may be configured like so, in your
core-site.xml file:

<property>
  <name>fs.defaultFS</name>
  <value>hdfs://mycluster</value>
</property>

  was:
We need to have only one of the two (fs.default.name or fs.defaultFS, and the former is deprecated).
If both are present then NN HA will be enabled/disabled based on what is read first, bad situation
!!

Following is description from NN HA in Apache docs:

fs.defaultFS - the default path prefix used by the Hadoop FS client when none is given.
Optionally, you may now configure the default path for Hadoop clients to use the new HA-enabled
logical URI. If you used "mycluster" as the nameservice ID earlier, this will be the value
of the authority portion of all of your HDFS paths. This may be configured like so, in your
core-site.xml file:

<property>
  <name>fs.defaultFS</name>
  <value>hdfs://mycluster</value>
</property>

    
> Change core-site.xml's fs.default.name to fs.defaultFS for 2.0 stack deployment
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-2789
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2789
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.0
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>             Fix For: 1.4.0
>
>         Attachments: AMBARI-2789.patch
>
>
> We need to have only one of the two (fs.default.name or fs.defaultFS, and the former
is deprecated). If both are present then NN HA will be enabled/disabled based on what is read
first.
> Following is description from NN HA in Apache docs:
> fs.defaultFS - the default path prefix used by the Hadoop FS client when none is given.
> Optionally, you may now configure the default path for Hadoop clients to use the new
HA-enabled logical URI. If you used "mycluster" as the nameservice ID earlier, this will be
the value of the authority portion of all of your HDFS paths. This may be configured like
so, in your core-site.xml file:
> <property>
>   <name>fs.defaultFS</name>
>   <value>hdfs://mycluster</value>
> </property>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message