[
https://issues.apache.org/jira/browse/AMBARI-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Falk updated AMBARI-13901:
---------------------------------
Description:
This defect is cloned from AMBARI-12851. Here is the original description:
Hadoop Env configuration defined at the stack level is managed only if HDFS
service is slected as part of the deployment. If HDFS is disabled and any
alternate FS includes hadoop-env in the stack, the configuration should be
understood by the Ambari code and corresponding hadoop-env.sh should be created
properly on the hadoop/ambari agent machines.
I don't believe that the issue has been
was:Hadoop Env configuration defined at the stack level is managed only if
HDFS service is slected as part of the deployment. If HDFS is disabled and any
alternate FS includes hadoop-env in the stack, the configuration should be
understood by the Ambari code and corresponding hadoop-env.sh should be created
properly on the hadoop/ambari agent machines.
> CLONE - The definition and hadling of hadoop-env should not be restrictive to
> HDFS
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-13901
> URL: https://issues.apache.org/jira/browse/AMBARI-13901
> Project: Ambari
> Issue Type: Bug
> Reporter: Nathan Falk
> Assignee: Sumit Mohanty
> Fix For: trunk
>
>
> This defect is cloned from AMBARI-12851. Here is the original description:
> Hadoop Env configuration defined at the stack level is managed only if HDFS
> service is slected as part of the deployment. If HDFS is disabled and any
> alternate FS includes hadoop-env in the stack, the configuration should be
> understood by the Ambari code and corresponding hadoop-env.sh should be
> created properly on the hadoop/ambari agent machines.
> I don't believe that the issue has been
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
