| clear query|facets|time |
Search criteria: .
Results from 31 to 40 from
121 (0.08s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[MAPREDUCE-5044] Have AM trigger jstack on task attempts that timeout before killing them - MapReduce - [issue]
|
|
...When an AM expires a task attempt it would be nice if it triggered a jstack output via SIGQUIT before killing the task attempt. This would be invaluable for helping users debug their h...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5044
Author: Jason Lowe,
2013-03-02, 18:12
|
|
|
[MAPREDUCE-4794] DefaultSpeculator generates error messages on normal shutdown - MapReduce - [issue]
|
|
...DefaultSpeculator can log the following error message on a normal shutdown of the ApplicationMaster:2012-11-13 01:35:31,841 ERROR [DefaultSpeculator background processing] org.apache.hadoop....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4794
Author: Jason Lowe,
2013-03-02, 14:05
|
|
|
[MAPREDUCE-4871] AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize - MapReduce - [issue]
|
|
...When the user needs to configure a larger split metainfo file size, mapred-default.xml points to the mapreduce.job.split.metainfo.maxsize property. However the ApplicationMaster actual...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4871
Author: Jason Lowe,
2013-03-01, 14:04
|
|
|
[MAPREDUCE-5037] JobControl logging when a job completes - MapReduce - [issue]
|
|
...JobControl emits logs, via the logging in Job.submit(), whenever a job is launched. It would be nice if it also logged when active jobs it is tracking complete and their final status (...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5037
Author: Jason Lowe,
2013-02-28, 17:07
|
|
|
[MAPREDUCE-4693] Historyserver should provide counters for failed tasks - MapReduce - [issue]
|
|
...Currently the historyserver is not providing counters for failed tasks, even though they are available via the AM as long as the job is still running. Those counters are lost when the ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4693
Author: Jason Lowe,
2013-02-28, 13:20
|
|
|
[MAPREDUCE-4831] Task commit can occur more than once due to AM retries - MapReduce - [issue]
|
|
...If a task attempt begins committing but the AM crashes before the task attempt completes then we could end up having the task commit again when the AM is relaunched. The subsequent AM ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4831
Author: Jason Lowe,
2013-02-27, 23:38
|
|
|
[MAPREDUCE-5000] TaskImpl.getCounters() can return the counters for the wrong task attempt when task is speculating - MapReduce - [issue]
|
|
...When a task is speculating and one attempt completes then sometimes the counters for the wrong attempt are aggregated into the total counters for the job. The scenario looks like this:...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5000
Author: Jason Lowe,
2013-02-14, 14:05
|
|
|
[MAPREDUCE-4982] AM hung with one pending map task - MapReduce - [issue]
|
|
...Saw a job that hung with one pending map task that never ran. The task was in the SCHEDULED state with a single attempt that was in the UNASSIGNED state. The AM looked like it wa...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4982
Author: Jason Lowe,
2013-02-13, 02:00
|
|
|
Re: [VOTE] Release hadoop-2.0.3-alpha - MapReduce - [mail # dev]
|
|
...+1 (non-binding) - Verified checksums and signatures on src and binary tarballs - Built from source - Deployed pseudo-distributed cluster and ran some example jobs Jason On...
|
|
|
Author: Jason Lowe,
2013-02-12, 23:56
|
|
|
[MAPREDUCE-4648] Diagnostics from AM are missing from job history - MapReduce - [issue]
|
|
...When a job fails during setup or commit, any diagnostics from the MapReduce ApplicationMaster are not available in the job history. Currently the diagnostics for the job are collected ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4648
Author: Jason Lowe,
2013-02-12, 20:59
|
|
|
|
