[ http://issues.apache.org/jira/browse/HADOOP-815?page=comments#action_12461560 ] Hadoop QA commented on HADOOP-815: ----------------------------------
-1, because the patch command could not apply the latest attachment (http://issues.apache.org/jira/secure/attachment/12348120/jt_memory_profiles.tgz) as a patch to trunk revision r489707. Please note that this message is automatically generated and may represent a problem with the automation system and not the patch. > Investigate and fix the extremely large memory-footprint of JobTracker > ---------------------------------------------------------------------- > > Key: HADOOP-815 > URL: http://issues.apache.org/jira/browse/HADOOP-815 > Project: Hadoop > Issue Type: Bug > Components: mapred > Affects Versions: 0.9.1 > Reporter: Arun C Murthy > Assigned To: Arun C Murthy > Fix For: 0.10.0 > > Attachments: 150k_1199_774.nps, 75k_jobs.nps, > HADOOP-815_20061220_1.patch, HADOOP-815_20061221_2.patch, > HADOOP-815_20061222_3.patch, HADOOP-815_20061230_4.patch, > jt_memory_profiles.tgz > > > The JobTracker's memory footprint seems excessively large, especially when > many jobs are submitted. > Here is the 'top' output of a JobTracker which has scheduled ~1k jobs thus > far: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > 31877 arunc 19 0 2362m 261m 13m S 14.0 12.9 24:48.08 java > Clearly VIRTual memory of 2364Mb v/s 261Mb of RESident memory is symptomatic > of this issue... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
