hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lu cheng (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5881) Simplify configuration related to task-memory-monitoring and memory-based scheduling
Date Mon, 05 Apr 2010 19:42:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853504#action_12853504
] 

lu cheng commented on HADOOP-5881:
----------------------------------

Hi guys,
If set mapred.cluster.max.map.memory.mb  and mapred.cluster.max.reduce.memory.mb in the mapred-site.xml,
for example, to be 3072, when I submit a grep job I get:
10/04/05 15:23:09 INFO mapred.FileInputFormat: Total input paths to process : 14
org.apache.hadoop.ipc.RemoteException: java.io.IOException: job_201004051501_0001(-1 memForMapTasks
-1 memForReduceTasks): Invalid job requirements.
        at org.apache.hadoop.mapred.JobTracker.checkMemoryRequirements(JobTracker.java:3864)
        at org.apache.hadoop.mapred.JobTracker.submitJob(JobTracker.java:3014)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)

        at org.apache.hadoop.ipc.Client.call(Client.java:740)
        at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:220)
        at org.apache.hadoop.mapred.$Proxy1.submitJob(Unknown Source)
        at org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:800)
        at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:730)
        at org.apache.hadoop.mapred.JobClient.runJob(JobClient.java:1249)
        at org.apache.hadoop.examples.Grep.run(Grep.java:69)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at org.apache.hadoop.examples.Grep.main(Grep.java:93)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:68)
        at org.apache.hadoop.util.ProgramDriver.driver(ProgramDriver.java:139)
        at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:64)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:156)


Also, If you set  mapred.cluster.map.memory.mb and mapred.cluster.reduce.memory.mb to be 512,
the system always prompts you that :
INFO mapred.JobClient: Task Id : attempt_201004051259_0001_r_000000_0, Status : FAILED
TaskTree [pid=32315,tipID=attempt_201004051259_0001_r_000000_0] is running beyond memory-limits.
Current usage : 556195840bytes. Limit : -1048576bytes. Killing task.


The version I deploy is 0.20.2.

It seems in some place the code use bytes, and in some place it uses MB.

Can someone fix this problem?


> Simplify configuration related to task-memory-monitoring and memory-based scheduling
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5881
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5881
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5881-20090526-branch-20.1.txt, HADOOP-5881-20090526.1.txt
>
>
> The configuration we have now is pretty complicated. Besides everything else, the mechanism
of not specifying parameters separately for maps and reduces leads to problems like HADOOP-5811.
This JIRA should address simplifying things and at the same time solving these problems.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message