/etc/hadoop/conf should reflect your gateway configs once you deploy client
configs. All roles act as gateways, so this should be the on your TT node
as well as your node with just a gateway. TT doesn't use the config in this
I'm assuming you meant you changed the gateway config "MapReduce Child Java
Maximum Heap Size" to 2GB.
I tried this in CM4.5, and it correctly gave me the following in
/etc/hadoop/conf/mapred-site.xml after deploying client configs:
It sounds like you did everything correctly, but I'm not able to reproduce
your issue. You may want to double-check your alternatives priority for
gateways for hdfs, mapreduce, and yarn. Normally mapreduce wins with 92
priority. You can also run "alternatives --display hadoop-conf" to make
sure it's picking up the right one.
Can you try deploying client configs and trying again? You can also try
downloading client configs and making sure it looks correct (also tested
this worked for me).
On Thu, Mar 14, 2013 at 7:36 PM, Benjamin Kim wrote:
I have set the MapReduce Max Java Heap Size to be 2GB and I/O Sort Memory
Buffer to 512MB under the Gateway (Base) configurations. I left the
settings under the TaskTracker (Base) configuration as default. After
restarting the mapreduce service in CM4.5 and deploying client
configurations, I see that across the cluster the settings are 1GB and
256MB respectively in /etc/hadoop/conf/mapred-site.xml. I guess this is to
be expected. But, when I check the gateway node, I expected the settings to
be 2GB and 512MB respectively, but they are not. They are 1GB and 256MB
respectively. Can someone tell me if there is something wrong here?