[
https://issues.apache.org/jira/browse/MAPREDUCE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750919#action_12750919
]
Sreekanth Ramakrishnan commented on MAPREDUCE-28:
-------------------------------------------------
Currently the job submission in JobTracker does the following steps during job
submission:
1. Create a new JobInProgress object.
2. Verify if the queue which job is submitted actually exists.
3. Check if the queue is running.
4. Check if the user hsa access for running job.
5. Check memory requirement.
And all the job tracker methods are delegation calls so we can directly call
the methods which directly call the QueueManager appropriate method, so we can
change the following test cases to directly call QueueManager appropriate
method instead of starting up MiniMRCluster:
- testAllEnabledACLForJobSubmission()
- testAllDisabledACLForJobSubmission()
- testUserDisabledACLForJobSubmission()
- testDisabledACLForNonDefaultQueue()
- testSubmissionToInvalidQueue()
- testEnabledACLForNonDefaultQueue()
- testUserEnabledACLForJobSubmission()
- testGroupsEnabledACLForJobSubmission()
- testAllEnabledACLForJobKill()
- testAllDisabledACLForJobKill()
- testOwnerAllowedForJobKill()
- testUserDisabledACLForJobKill()
- testUserEnabledACLForJobKill()
- testUserDisabledForJobPriorityChange()
The test case testStateRefresh() can also be made unit test instead of starting
up a cluster same way as we test acls refresh.
We can then add a new integration test case to test following conditions:
1. acls for a user in a queue where he is denied/given access to submit and
manage a job
2. State of the queue.
> TestQueueManager takes too long and times out some times
> --------------------------------------------------------
>
> Key: MAPREDUCE-28
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-28
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Amareshwari Sriramadasu
>
> TestQueueManager takes long time for the run and timeouts sometimes.
> See the failure at
> http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3875/testReport/.
> Looking at the console output, before the test finsihes, it was timed-out.
> On my machine, the test takes about 5 minutes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
