This may happen if your YARN service is misconfigured w.r.t. memory resources. An MR job requires 1.5g for its AppMaster, and subsequently 1g for each task. Therefore, NodeManagers should be publishing at least 2.5g or 3g for MR jobs to run.

Can you ensure your value in CM -> YARN -> Configuration, for field
"yarn.nodemanager.resource.memory-mb" is set to at least 3 GB or higher? If it isn't, please set it appropriately as per your machine's ability, and restart the YARN service and retry the job submission.

You can also alternatively reduce the default memory demands via client-side properties yarn.app.mapreduce.am.resource.mb (for the MR AppMaster) and set of mapreduce.map.memory.mb/mapreduce.reduce.memory.mb (for the Tasks). These properties accept integer values in MB units.