How to control and monitor the concurrency of MAP/reduce in yarn

Configuration recommendations:

1.
In MR1, The mapred. tasktracker. Map. Tasks. Maximum and mapred. tasktracker. Reduce. Tasks. Maximum properties dictated how many map and reduce slots each tasktracker had.

These properties no longer exist in yarn. instead, yarn uses yarn. nodemanager. resource. memory-MB and yarn. nodemanager. resource. CPU-vcores, which control the amount of memory and CPU on each node, both available to both maps and reduces

Essentially:
Yarn has no tasktrackers, but just generic nodemanagers. Hence, there's no more map slots and reduce slots separation. Everything depends on the amount of memory in use/demanded

2.

Using the Web UI you can get lot of monitoring/admin kind of info:

Namenode-http: //: 50070/
Resource Manager-http: //: 8088/

For other configurations, refer:

1. There is a good guide on Yarn configuration from hortonworks
2. You may analyze your job in job history server. It usually may be found on port 19888. ambari andganglia are also very good for cluster utilization measurement.