Description
This is MapReduce part of HADOOP-6332
Attachments
Attachments
Issue Links
- blocks
-
HADOOP-6786 test-patch needs to verify Herriot integrity
- Resolved
-
MAPREDUCE-1646 Task Killing tests
- Open
-
MAPREDUCE-1713 Utilities for system tests specific.
- Resolved
- is blocked by
-
HADOOP-6771 Herriot's artifact id for Maven deployment should be set to hadoop-core-instrumented
- Closed
-
HADOOP-6875 [Herriot] Cleanup of temp. configurations is needed upon restart of a cluster
- Closed
- is depended upon by
-
MAPREDUCE-1790 Automatic resolution of Lzo codecs is needed.
- Resolved
-
MAPREDUCE-1827 [Herriot] Task Killing/Failing tests for a streaming job.
- Open
-
MAPREDUCE-1898 [Herriot] Implement a functionality for getting the job summary information of a job.
- Open
-
MAPREDUCE-1957 [Herriot] Test Job cache directories cleanup after job completes.
- Open
-
MAPREDUCE-1963 [Herriot] TaskMemoryManager should log process-tree's status while killing tasks
- Open
-
MAPREDUCE-1693 Process tree clean up of either a failed task or killed task tests.
- Resolved
-
MAPREDUCE-1710 Process tree clean up of exceeding memory limit tasks.
- Resolved
-
MAPREDUCE-1731 Process tree clean up suspended task tests.
- Resolved
-
MAPREDUCE-1809 Ant build changes for Streaming system tests in contrib projects.
- Resolved
-
MAPREDUCE-1899 [Herriot] Test jobsummary information for different jobs.
- Resolved
-
HADOOP-6839 [Herriot] Implement a functionality for getting the user list for creating proxy users.
- Closed
-
MAPREDUCE-1812 New properties for suspend and resume process.
- Closed
-
MAPREDUCE-1896 [Herriot] New property for multi user list.
- Closed
- is related to
-
HADOOP-6332 Large-scale Automated Test Framework
- Closed
- is required by
-
MAPREDUCE-1760 Herriot tests for MapReduce should support submission into a specific queue
- Open
-
MAPREDUCE-1616 Automate system test case for checking the file permissions in mapred.local.dir
- Open
-
MAPREDUCE-1654 Automate the job killing system test case.
- Open
-
MAPREDUCE-1671 Test scenario for "Killing Task Attempt id till job fails"
- Open
-
MAPREDUCE-1672 Create test scenario for "distributed cache file behaviour, when dfs file is not modified"
- Open
-
MAPREDUCE-1676 Create test scenario for "distributed cache file behaviour, when dfs file is modified"
- Open
-
MAPREDUCE-1677 Test scenario for a distributed cache file behaviour when the file is private
- Open
-
MAPREDUCE-1730 Automate test scenario for successful/killed jobs' memory is properly removed from jobtracker after these jobs retire.
- Resolved
-
MAPREDUCE-1741 Automate the test scenario of job related files are moved from history directory to done directory
- Resolved
-
MAPREDUCE-1794 Test the job status of lost task trackers before and after the timeout.
- Resolved