hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-5582) Setting mapred.job.reduce.memory.mb to 0 from a job with CapacityTracker leads to inconsistent state in JVMManager
Date Sat, 09 May 2015 00:22:59 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli resolved MAPREDUCE-5582.
------------------------------------------------
    Resolution: Won't Fix

We haven't done a 1.x release in ~2 years. Unlikely this issue is going to be fixed/released.
If you see the same issue in 2.x, please file a new ticket. Closing this as Won't Fix. Thanks.

> Setting mapred.job.reduce.memory.mb to 0 from a job with CapacityTracker leads to inconsistent
state in JVMManager
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5582
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5582
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: capacity-sched
>            Reporter: Mikhail Davidov
>            Priority: Critical
>
> If a job sets mapred.job.reduce.memory.mb to 0 the capacity scheduler incorrectly allocates
resources eventually causing "Inconsistent state!!! JVM Manager reached an unstable state
while reaping a JVM for task" errors from the JVMManager killing all TaskTrackers that have
been used for the job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message