| clear query|facets|time |
Search criteria: .
Results from 61 to 70 from
116 (0.143s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[MAPREDUCE-4804] Counters for the applicationmaster - MapReduce - [issue]
|
|
...We should provide counters for the AM itself to track interesting items such as time spent garbage collecting, cpu time spent, etc. Currently there are no counters specifically for the...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4804
Author: Jason Lowe,
2012-11-16, 21:21
|
|
|
[MAPREDUCE-4801] ShuffleHandler can generate large logs due to prematurely closed channels - MapReduce - [issue]
|
|
...We ran into an instance where many nodes on a cluster ran out of disk space because the nodemanager logs were huge. Examining the logs showed many, many shuffle errors due to either Cl...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4801
Author: Jason Lowe,
2012-11-16, 13:21
|
|
|
[MAPREDUCE-4785] TestMRApp occasionally fails - MapReduce - [issue]
|
|
...TestMRApp is failing occasionally with this error:testUpdatedNodes(org.apache.hadoop.mapreduce.v2.app.TestMRApp): Expecting 2 more completion events for killed expected:<4> but was:<...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4785
Author: Jason Lowe,
2012-11-10, 23:58
|
|
|
[MAPREDUCE-4767] AM should flush AMInfos to history file - MapReduce - [issue]
|
|
...When the ApplicationMaster starts up and generates (and potentially recovers) AMInfo records for the history file, those events should be flushed to disk in case the AM crashes badly. ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4767
Author: Jason Lowe,
2012-11-01, 22:48
|
|
|
[MAPREDUCE-4521] mapreduce.user.classpath.first incompatibility with 0.20/1.x - MapReduce - [issue]
|
|
...In Hadoop 0.20 or 1.x, jobs can specify the user's classpath should appear first by setting the property mapreduce.user.classpath.first to true in the job configuration. However in Had...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4521
Author: Jason Lowe,
2012-10-17, 14:21
|
|
|
[MAPREDUCE-4020] Web services returns incorrect JSON for deep queue tree - MapReduce - [issue]
|
|
...When the capacity scheduler is configured for more than two levels of queues, the web services API returns incorrect JSON for the subQueues field of some parent queues. The "subQueues"...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4020
Author: Jason Lowe,
2012-10-11, 18:48
|
|
|
[MAPREDUCE-4646] client does not receive job diagnostics for failed jobs - MapReduce - [issue]
|
|
...When a job fails the client is not showing any diagnostics. For example, running a fail job results in this not-so-helpful message from the client:2012-09-07 21:12:00,649 INFO [m...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4646
Author: Jason Lowe,
2012-10-11, 18:48
|
|
|
[MAPREDUCE-4228] mapreduce.job.reduce.slowstart.completedmaps is not working properly to delay the scheduling of the reduce tasks - MapReduce - [issue]
|
|
...If no more map tasks need to be scheduled but not all have completed, the ApplicationMaster will start scheduling reducers even if the number of completed maps has not met the mapreduce.job....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4228
Author: Jason Lowe,
2012-10-11, 18:48
|
|
|
[MAPREDUCE-4705] Historyserver links expire before the history data does - MapReduce - [issue]
|
|
...The historyserver can serve up links to jobs that become useless well before the job history files are purged. For example on a large, heavily used cluster we can end up rotating throu...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4705
Author: Jason Lowe,
2012-10-09, 15:00
|
|
|
[MAPREDUCE-4714] Historyserver retrieves job from jobID more often than necessary - MapReduce - [issue]
|
|
...When serving up a web page for job history, AppController.requireJob() is converting from a jobID to a job twice when it only needs to do it once. The resulting job is stored into the ...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4714
Author: Jason Lowe,
2012-10-08, 21:18
|
|
|
|
