I figured out what the issue was. My configuration object was not able to get mapreduce.framework.name as "yarn" from mapred-site.xml. So I was overiding mapreduce.framework.name in driver. So that it can pick YarnClientProtocolProvider instead of LocalClientProtocolProvider.    When yarn is picked up it launched mapreduce job.      ... View more