[jira] Commented: (MAPREDUCE-1020) Add more unit tests to test the queue refresh feature MAPREDUCE-893

["Vinod K V (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781862#action_12781862 ] 

Vinod K V commented on MAPREDUCE-1020:
--------------------------------------

Here are some of the pending tests that come to my mind:
 - verify that support for priorities cannot be changed from enabled to disabled and vice versa during refresh
 - verify the consistency in state of JobQueuesManager
    -- what happens to the 'jobQueues' list? (Not sure, myself)
    -- the actual lits of running and waiting jobs
 - JobInitializationPoller
  -- per-queue maxUsersAllowedToInitialize
  -- per-queue maxJobsPerUserToInitialize
  -- running-state of the poller
    -- jobs with the poller
    -- how changed ulimits affect the after-refresh behaviour of the poller
 - verify the running-state of the scheduler
    -- numJobsByUser
    -- numWaitingJobs
    -- maxCapacityPercent
    -- queue-scheduling-context objects
    -- map/reduce task-scheduling information
      -- cluster-capacity
      -- numRunningTasks
      -- numSlotsOccupied
      -- maxCapacity
      -- numSlotsOccupiedByUser

> Add more unit tests to test the queue refresh feature MAPREDUCE-893
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1020
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1020
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.21.0
>            Reporter: Vinod K V
>             Fix For: 0.21.0
>
>
> MAPREDUCE-893 included unit tests verifying the sanity of the refresh feature - both the queue properities' refresh as well as the scheduler properties' refresh. The test suite can and should be expanded. This will help easily identifying issues that will otherwise be caught during manual testing. For e.g., during manual testing of MAPREDUCE-893, we identified an NPE in the scheduler iteration occuring during heartbeat, which could have been easily identified by unit tests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.