ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BORIE (JIRA)" <>
Subject [jira] [Commented] (AMBARI-1284) Bug with jobtracker installation when deploying on a 4-nodes cluster
Date Thu, 31 Jan 2013 12:57:12 GMT


BORIE commented on AMBARI-1284:

Hi Mahadev, 

I've solved my issue. In fact, we are mounting /var/log as a dedicated partition on our servers.

And MapReduce default configuration in Ambari uses /var/log/mapred (and all other mounted
partitions on the system) as local working directories. I'm sorry, didn't notice that. 

But mapreduce also uses this partition /var/log/hadoop/mapred as its logging destination,
so there was a conflict between the 2 manifests which define it in different contexts (jobtracker.pp
and service.pp)

Removing /var/log/hadoop/mapred from the list of mapreduce local working directories configured
by default solved my issue. 

This ticket can be closed, 


> Bug with jobtracker installation when deploying on a 4-nodes cluster
> --------------------------------------------------------------------
>                 Key: AMBARI-1284
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>         Environment: 4 CentOS 6.3 up-to-date nodes
>            Reporter: BORIE
> Hello, 
> I'm facing an issue when deploying with Ambari (in HDP 1.2 context). All is fine until
the installation step : the jobtracker installation fails with the following Puppet message
> Duplicate definition: Hdp::Directory_recursive_create[/var/log/hadoop/mapred] is already
defined in file /var/lib/ambari-agent/puppet/modules/hdp-hadoop/manifests/jobtracker.pp at
line 93; cannot redefine at /var/lib/ambari-agent/puppet/modules/hdp-hadoop/manifests/service.pp:85
on node *****
> When installing my cluster in pseudo-distributed mode on a single node, I didn't encounter
this problem and the deployment completes successfully. 
> Regards, 
> Fran├žois

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:

View raw message