Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 20 Aug 2015 17:41:46 +0000 (UTC)
From: "Vijay Srinivasaraghavan (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12857600.1440092503000.121964.1440092506543@Atlassian.JIRA>
In-Reply-To: <JIRA.12857600.1440092503000@Atlassian.JIRA>
References: <JIRA.12857600.1440092503000@Atlassian.JIRA>
 <JIRA.12857600.1440092503023@arcas>
Subject: [jira] [Created] (AMBARI-12837) Server component should read HCFS
 type info from stack and propagate it in dictionary for agent and UI to
 consume
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vijay Srinivasaraghavan created AMBARI-12837:
------------------------------------------------

             Summary: Server component should read HCFS type info from stack and propagate it in dictionary for agent and UI to consume
                 Key: AMBARI-12837
                 URL: https://issues.apache.org/jira/browse/AMBARI-12837
             Project: Ambari
          Issue Type: Task
            Reporter: Vijay Srinivasaraghavan


UI and agent code is using namenode configuration as a validation to check if HDFS is selected or not and perform some HDFS specific operations like creating /tmp directory, reading hadoop-env configurations like hdfs_log_dir_prefix, dropping fast-hdfs-resource.jar etc., because of which the configurations defined for HCFS types are not getting populated. The ambari server component should tarverse thhrough the stack configuration and populate (hadoop-env or cluster-env) dictionary if HCFS file system is asscoated as part of the stack. The dictionary configuration should be used in UI and agent code to allow FS operations require to bootstrap the cluster deployment.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)