| clear query|facets|time |
Search criteria: .
Results from 41 to 50 from
121 (0.12s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[MAPREDUCE-4818] Easier identification of tasks that timeout during localization - MapReduce - [issue]
|
|
...When a task is taking too long to localize and is killed by the AM due to task timeout, the job UI/history is not very helpful. The attempt simply lists a diagnostic stating it was kil...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4818
Author: Jason Lowe,
2013-02-12, 20:57
|
|
|
[MAPREDUCE-4999] AM attempt ended up in ERROR state and generated history after node decommissioned - MapReduce - [issue]
|
|
...Saw a case where a job recorded history for an app attempt that ended up in the ERROR state after the node the AM was running on was decommissioned. When the node was decommissioned, t...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4999
Author: Jason Lowe,
2013-02-11, 16:07
|
|
|
[MAPREDUCE-4797] LocalContainerAllocator can loop forever trying to contact the RM - MapReduce - [issue]
|
|
...If LocalContainerAllocator has trouble communicating with the RM it can end up retrying forever if the nature of the error is not a YarnException.This can be particulary bad if the connectio...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4797
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4771] KeyFieldBasedPartitioner not partitioning properly when configured - MapReduce - [issue]
|
|
...Relative to Hadoop 0.20/1.x, KeyFieldBasedPartitioner is not distributing across partitions properly when configured. This is related to the double-configure issue as described in HADO...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4771
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4666] JVM metrics for history server - MapReduce - [issue]
|
|
...It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4666
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4741] WARN and ERROR messages logged during normal AM shutdown - MapReduce - [issue]
|
|
...The ApplicationMaster is logging WARN and ERROR messages during normal shutdown, and some users are misinterpreting these as serious problems. For example:2012-10-02 13:58:50,247 ERROR...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4741
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4733] Reducer can fail to make progress during shuffle if too many reducers complete consecutively - MapReduce - [issue]
|
|
...TaskAttemptListenerImpl implements getMapCompletionEvents by calling Job.getTaskAttemptCompletionEvents with the same fromEvent and maxEvents passed in from the reducer and then filtering th...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4733
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4730] AM crashes due to OOM while serving up map task completion events - MapReduce - [issue]
|
|
...We're seeing a repeatable OOM crash in the AM for a task with around 30000 maps and 3000 reducers. Details to follow....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4730
Author: Jason Lowe,
2013-02-06, 17:05
|
|
|
[MAPREDUCE-4955] NM container diagnostics for excess resource usage can be lost if task fails while being killed - MapReduce - [issue]
|
|
...When a nodemanager kills a container for being over resource budgets, it provides a diagnostics message for the container status explaining why it was killed. However this message can ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4955
Author: Jason Lowe,
2013-02-06, 00:25
|
|
|
[MAPREDUCE-4960] Unexpected extra results when using the task attempt table search - MapReduce - [issue]
|
|
...When using the search box on the web UI to search for a specific task number (e.g.: "0831"), sometimes unexpected extra results are shown. Using the web browser's built-in search-withi...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4960
Author: Jason Lowe,
2013-01-28, 22:12
|
|
|
|
