java - Hadoop Mapper is failing because of "Container killed by the ApplicationMaster" -


i trying execute map reduce program on hadoop.

when submit job hadoop single node cluster. job getting created failing message

"container killed applicationmaster"

the input used of size 10 mb.

when used same script of input file 400 kb, got succeded. failing the input file of size 10 mb.

the complete log displayed in terminal follows.

    15/05/29 09:52:16 warn util.nativecodeloader: unable `load native-  hadoop library platform... using builtin-java classes      applicable submitting job on cluster... 15/05/29 09:52:17 info client.rmproxy: connecting resourcemanager @ /0.0.0.0:8032 15/05/29 09:52:18 info input.fileinputformat: total input paths process : 1 15/05/29 09:52:18 info mapreduce.jobsubmitter: number of splits:1 15/05/29 09:52:19 info mapreduce.jobsubmitter: submitting tokens job: job_1432910768528_0001 15/05/29 09:52:19 info impl.yarnclientimpl: submitted application application_1432910768528_0001 15/05/29 09:52:19 info mapreduce.job: url track job: http://localhost:8088/proxy/application_1432910768528_0001/ 15/05/29 09:52:19 info mapreduce.job: running job: job_1432910768528_0001 15/05/29 09:52:29 info mapreduce.job: job job_1432910768528_0001 running in uber mode : false 15/05/29 09:52:29 info mapreduce.job:  map 0% reduce 0% 15/05/29 09:52:41 info mapreduce.job:  map 100% reduce 0% 15/05/29 10:03:01 info mapreduce.job:  map 0% reduce 0% 15/05/29 10:03:01 info mapreduce.job: task id : attempt_1432910768528_0001_m_000000_0, status : failed attemptid:attempt_1432910768528_0001_m_000000_0 timed out after 600 secs container killed applicationmaster. container killed on request. exit code 143 container exited non-zero exit code 143 

my mapper here triggering other program going process input file here. program getting trigger mapper consumes lots of memory.

so please me in regard.

include below properties in yarn-site.xml , restart vm,

<property>    <name>yarn.nodemanager.vmem-check-enabled</name>    <value>false</value>    <description>whether virtual memory limits enforced containers</description> </property>  <property>    <name>yarn.nodemanager.vmem-pmem-ratio</name>    <value>4</value>    <description>ratio between virtual memory physical memory when setting memory limits containers</description> </property> 

Comments

Popular posts from this blog

Java 3D LWJGL collision -

spring - SubProtocolWebSocketHandler - No handlers -

methods - python can't use function in submodule -