Also worth to note, i tried that with 3 different clusters. 2 of them are showing 0 memory, only my pseudo distributed apache cluster is giving something like 'App total resource memory: 7168 cpu: 0 taskAllocations: 0’. Same code used.
Johannes On 19 Aug 2014, at 09:12, Johannes Zillmann <[email protected]> wrote: > This is in the logs > YarnTaskSchedulerService: App total resource memory: 0 cpu: 0 > taskAllocations: 0 > > Looking at the resource tracker’s webui i can see e.g. 7 of 22 GB used at > this moment. > > Johannes > > On 18 Aug 2014, at 22:52, Bikas Saha <[email protected]> wrote: > >> Looks for this log line >> LOG.info("App total resource memory: " + totalResources.getMemory() + >> " cpu: " + totalResources.getVirtualCores() + >> " taskAllocations: " + taskAllocations.size()); >> >> -----Original Message----- >> From: Bikas Saha [mailto:[email protected]] >> Sent: Monday, August 18, 2014 1:51 PM >> To: [email protected] >> Subject: RE: context.getTotalAvailableResource().getMemory() is 0 >> >> Your cluster Resource Manager returned 0 available memory when the app >> started. >> >> Bikas >> >> -----Original Message----- >> From: Johannes Zillmann [mailto:[email protected]] >> Sent: Monday, August 18, 2014 12:37 PM >> To: [email protected] >> Subject: context.getTotalAvailableResource().getMemory() is 0 >> >> Hey folks, >> >> in my InputInitializer i'm doing >> >> InputInitializerContext context = getContext(); >> int memory = context.getTotalAvailableResource().getMemory(); >> >> The returned memory is 0. Any idea what could be the reason for that ? >> >> Johannes >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >
