| clear query|facets|time |
Search criteria: .
Results from 1 to 10 from
121 (0.109s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[MAPREDUCE-5261] TestRMContainerAllocator is exiting and failing the build - MapReduce - [issue]
|
|
...Recent builds are failing because TestRMContainerAllocator is exiting rather than succeeding or failing....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5261
Author: Jason Lowe,
2013-05-23, 02:50
|
|
|
[MAPREDUCE-5268] Improve history server startup performance - MapReduce - [issue]
|
|
...The history server can easily take many minutes to startup when there are a significant number of jobs to scan in the done directory. However the scanning of files is not the bottlenec...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5268
Author: Jason Lowe,
2013-05-23, 00:15
|
|
|
[MAPREDUCE-5267] History server should be more robust when cleaning old jobs - MapReduce - [issue]
|
|
...Ran across a situation where an admin user had accidentally created a directory in one of the date directories under /mapred/history/done/ that was not readable by the historyserver user. &n...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5267
Author: Jason Lowe,
2013-05-22, 21:03
|
|
|
[MAPREDUCE-5266] Ability to refresh retention settings on history server - MapReduce - [issue]
|
|
...It would be very useful if the job and log retention settings of the history server could be refreshed without restarting the history server. This would include such things as: how man...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5266
Author: Jason Lowe,
2013-05-22, 17:17
|
|
|
[MAPREDUCE-5265] Ability to refresh super user groups on history server - MapReduce - [issue]
|
|
...The history server needs the ability to refresh the super user groups configurations without requiring a restarting the history server. This is analogous to the -refreshSuperUserGroups...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5265
Author: Jason Lowe,
2013-05-22, 17:14
|
|
|
Re: [VOTE] Plan to create release candidate for 0.23.8 - MapReduce - [mail # dev]
|
|
...+1 On 05/17/2013 04:10 PM, Thomas Graves wrote:...
|
|
|
Author: Jason Lowe,
2013-05-22, 13:36
|
|
|
[MAPREDUCE-5124] AM lacks flow control for task events - MapReduce - [issue]
|
|
...The AM does not have any flow control to limit the incoming rate of events from tasks. If the AM is unable to keep pace with the rate of incoming events for a sufficient period of time...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5124
Author: Jason Lowe,
2013-05-22, 08:54
|
|
|
[MAPREDUCE-5257] TestContainerLauncherImpl fails - MapReduce - [issue]
|
|
...TestContainerLauncherImpl is hanging and eventually being killed by the surefire timeout which fails a maven test build....
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5257
Author: Jason Lowe,
2013-05-20, 14:21
|
|
|
[MAPREDUCE-4927] Historyserver 500 error due to NPE when accessing specific counters page for failed job - MapReduce - [issue]
|
|
...Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserv...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-4927
Author: Jason Lowe,
2013-05-18, 14:36
|
|
|
[MAPREDUCE-5059] Job overview shows average merge time larger than for any reduce attempt - MapReduce - [issue]
|
|
...When looking at a job overview page on the history server, the Average Merge Time is often reported with a value that is far larger than the Elapsed Merge Time shown for any reduce task atte...
|
|
|
http://issues.apache.org/jira/browse/MAPREDUCE-5059
Author: Jason Lowe,
2013-05-18, 13:39
|
|
|
|
