But I can see the jobtracker OOME issue fixed in hadoop - 1.2.1 version as
per the hadoop release notes as below.
Please check this URL,
How come the issue still persist? I'm I asking a valid thing.
Do I need to configure anything our I missing anything.
Please help. Appreciate your response.
On Oct 12, 2013 7:57 PM, "Viswanathan J" <[EMAIL PROTECTED]> wrote:
> Thanks Antonio, hope the memory leak issue will be resolved. Its really
> nightmare every week.
> In which release this issue will be resolved?
> How to solve this issue, please help because we are facing in production
> Please share the configuration and cron to do that cleanup process.
> On Oct 12, 2013 7:31 PM, "Antonios Chalkiopoulos" <[EMAIL PROTECTED]>
>> "After restart the JT, within a week getting OOME."
>> Viswa, we were having the same issue in our cluster as well - roughly
>> every 5-7 days getting OOME.
>> The heap size of the Job Tracker was constantly increasing due to a
>> memory leak that will hopefully be fixed in newest releases.
>> There is a configuration change in the JobTracker that will disable a
>> functionality regarding cleaning up staging files i.e.
>> /user/build/.staging/* - but that means that you will have to handle the
>> staging files through a cron / jenkins task
>> I'll get you the configuration on Monday..
>> On Friday, 11 October 2013 18:08:55 UTC+1, Viswanathan J wrote:
>>> I'm running a 14 nodes of Hadoop cluster with datanodes,tasktrackers
>>> running in all nodes.
>>> *Apache Hadoop :* 1.2.1
>>> It shows the heap size currently as follows:
>>> *Cluster Summary (Heap Size is 5.7/8.89 GB)*
>>> In the above summary what is the *8.89* GB defines? Is the *8.89*defines maximum heap size for Jobtracker, if yes how it has
>>> been calculated.
>>> Hope *5.7* is currently running jobs heap-size, how it is calculated.
>>> Have set the jobtracker default memory size in hadoop-env.sh
>>> Have set the mapred.child.java.opts value in mapred-site.xml as,
>>> Even after setting the above property, getting Jobtracker OOME issue.
>>> How the jobtracker memory gradually increasing. After restart the JT,
>>> within a week getting OOME.
>>> How to resolve this, it is in production and critical? Please help.
>>> Thanks in advance.
>> You received this message because you are subscribed to the Google Groups
>> "CDH Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to cdh-user+[EMAIL PROTECTED].
>> For more options, visit