ris
>
> From: Chris Riccomini [criccom...@linkedin.com]
> Sent: Wednesday, September 21, 2011 1:42 PM
> To: mapreduce-dev@hadoop.apache.org
> Subject: Re: ApplicationMaster Memory Usage
>
> For the record, I bumped to 4096 for memory resour
thinks my app is taking 2 gigs, and how to fix this.
Cheers,
Chris
From: Chris Riccomini [criccom...@linkedin.com]
Sent: Wednesday, September 21, 2011 1:42 PM
To: mapreduce-dev@hadoop.apache.org
Subject: Re: ApplicationMaster Memory Usage
For the record, I
;>this
>> }
>>
>> def unregisterWithResourceManager(state: String): ApplicationMasterHelper
>> = {
>>val finReq = Records.newRecord(classOf[FinishApplicationMasterRequest])
>>finReq.setAppAttemptId(appAttemptId)
>> finReq.setFinalState(s
alli [vino...@hortonworks.com]
Sent: Wednesday, September 21, 2011 11:52 AM
To: mapreduce-dev@hadoop.apache.org
Subject: Re: ApplicationMaster Memory Usage
Actually MAPREDUCE-2998 is only related to MRV2, so that isn't related.
Somehow, your JVM itself is taking so much of virtual memory. Are you
1)
>request.setPriority(pri)
>capability.setMemory(128)
>request.setCapability(capability)
>req.setResponseId(requestId)
>req.setApplicationAttemptId(appAttemptId)
>req.addAllAsks(Lists.newArrayList(request))
>req.addAllReleases(release)
>request
}
________
From: Vinod Kumar Vavilapalli [vino...@hortonworks.com]
Sent: Wednesday, September 21, 2011 10:08 AM
To: mapreduce-dev@hadoop.apache.org
Subject: Re: ApplicationMaster Memory Usage
Yes, the process-dump clearly tells that this is MAPREDUCE-2998.
+Vin
Yes, the process-dump clearly tells that this is MAPREDUCE-2998.
+Vinod
(With a smirk to see his container-memory-monitoring code in action)
On Wed, Sep 21, 2011 at 10:26 PM, Arun C Murthy wrote:
> I'll bet you are hitting MR-2998.
>
> From the changelog:
>
>MAPREDUCE-2998. Fixed a bug in
Appears likely! Will svn up and try. Glad it got committed today. :)
On 9/21/11 9:56 AM, "Arun C Murthy" wrote:
> I'll bet you are hitting MR-2998.
>
> From the changelog:
>
> MAPREDUCE-2998. Fixed a bug in TaskAttemptImpl which caused it to fork
> bin/mapred too many times. Contributed b
I'll bet you are hitting MR-2998.
From the changelog:
MAPREDUCE-2998. Fixed a bug in TaskAttemptImpl which caused it to fork
bin/mapred too many times. Contributed by Vinod K V.
Arun
On Sep 21, 2011, at 9:52 AM, Chris Riccomini wrote:
> Hey Guys,
>
> My ApplicationMaster is being killed
