|| at May 8, 2013 at 6:20 pm
Hi and thanks for the quick reply :-)
The JobTracker port number is set to 8021 (I think that is the default
value) and it is not my intention to change that.
Regarding oozie, the oozie-site.xml is located at
"myServerFE:7180/cmf/process/153/config?filename=oozie-site.xml" and for
some reason in the whitelist it has the following:
I never changed the job tracker port during the installation or after.
The only strange thing during the installation was that for some of the
hosts there was a different Role group automatically assigned, like
DataNode(1) instead of DataNode(Base). Cloudera Manager was claiming that
this was due to a different hardware configuration while my hosts are all
exactly the same virtual machines.
It would be good if you could explain me what could've possibly happened
and if there is a way to fix the configuration without another re-install
of the system.
Thanks and kind regards,
On Wednesday, 8 May 2013 19:47:21 UTC+2, Vikram Srivastava wrote:
To set the JobTracker port number, you need to goto your MapReduce service
in CM, and then "Configuration". On the left side you'll see configuration
sections for "JobTracker (Base)" > "Ports and Addresses". You can set the
port numbers there. Remember to restart MR and Oozie after changing any
Regarding oozie - Can you tell me the location of your oozie-site.xml
where you see 8032 port for JT?
The OS is actually "Red Hat Enterprise Linux Server release 6.3
(Santiago)" and not CentOS
On Wednesday, 8 May 2013 18:23:36 UTC+2, Robert wrote:
I am using the free version of Cloudera Manager 4.5 to install all the
services on my cluster composed by 8 machines (1 FE, 6 DN, 1 NN).
While on another cluster I had no major troubles and all was nicely
configured and working out of the box, on the current cluster (exactly the
same as the first one) the system is behaving differently.
In the oozie-site.xml the jobtracker whitelist port is set to 8032 while
in the mapreduce settings the jobtracker port is actually 8021. Having the
free version of cloudera manager, I cannot find how can I edit
oozie-site.xml to allow any jobtracker in the whitelist.
The jobtracker is on the namenode and I can see that both 8021 and 8032
are being used and I just cannot explain that behaviour. The cloudera
manager was installed on a clean CentOS and the roles are exactly the same
as my other cluster where things work fine.
I really hope someone can help me as this is really frustrating. I even
cleaned-up all the machines and reinstalled Cloudera manager but still
ended up with the same wrong configuration.