<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: MapReduce application failed with OutOfMemoryError in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/MapReduce-application-failed-with-OutOfMemoryError/m-p/56021#M36633</link>
    <description>I don't know of anything that would allow it to read the configuration files from the other file. The difference in mapred and mapreduce settings is the MR API. I think it is possible then that the MR app you have is using the older API and maybe that is why the mapred settings were working before.&lt;BR /&gt;&lt;BR /&gt;You can check the configuration settings for each MR job through the RM UI. Use that to verify the exact settings used in each settings.&lt;BR /&gt;&lt;BR /&gt;On the resource usage, the number of maps is determined by the input. Are you positive that the same amount of data and blocks was being used by the app in each run?</description>
    <pubDate>Fri, 16 Jun 2017 17:12:26 GMT</pubDate>
    <dc:creator>mbigelow</dc:creator>
    <dc:date>2017-06-16T17:12:26Z</dc:date>
  </channel>
</rss>

