Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
At present, we only have unit tests that make use of FakeTaskManager and that only test the proper functionality of capacity scheduler in isolation. Many issues unearthed recently proved that this is not enough and that it is required to have end-to-end tests so that real JT is brought into the picture and with that the interaction of the scheduler with JT. This issue along with few other related jiras should automate and replace the end-to-end tests that are now manually done by QA, using MiniMRCluster.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-524 Have end to end tests based on MiniMRCluster to verify the correct behaviour of job initialization.
- Resolved
- is blocked by
-
MAPREDUCE-293 Need value for Running, Completed and Failed maps and reduces for a job.
- Open
- relates to
-
MAPREDUCE-518 Have end to end tests based on MiniMRCluster to verify correct behaviour of slot reclamation by queues.
- Resolved
-
MAPREDUCE-524 Have end to end tests based on MiniMRCluster to verify the correct behaviour of job initialization.
- Resolved
-
MAPREDUCE-525 Have end to end tests based on MiniMRCluster to verify the correct behaviour of job priorities.
- Resolved
-
MAPREDUCE-531 Have end to end tests based on MiniMRCluster to verify the correct behaviour of user limits
- Resolved