Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-1807

TestQueueManager can take long enough to time out

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Sometimes TestQueueManager takes such a long time that the JUnit engine times out and declares it a failure. We should fix this, possibly by splitting the file's 19 test cases into two or more manageable test sets.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        5h 20m 1 Amareshwari Sriramadasu 21/May/10 09:05
        Hide
        Dick King added a comment -

        I agree.

        Show
        Dick King added a comment - I agree.
        Amareshwari Sriramadasu made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Duplicate [ 3 ]
        Hide
        Amareshwari Sriramadasu added a comment -

        I agree it is fixed by MAPREDUCE-28. Resolving as duplicate
        Dick, please re-open if you don't think so.

        Show
        Amareshwari Sriramadasu added a comment - I agree it is fixed by MAPREDUCE-28 . Resolving as duplicate Dick, please re-open if you don't think so.
        Hide
        Sreekanth Ramakrishnan added a comment -

        Currently in trunk and .21 of hadoop, we have removed all the MiniMRCluster test to a new test case and TestQueueManager is plain unit test. All the integration tests have been moved to TestQueueManagerWithJobTracker which has only 3 test cases and all of the same runs under a minute even. Currently in latest build the same took only 30 seconds.

        This was done as part of MAPREDUCE-28.

        Isn't solution at MAPREDUCE-28 sufficient?

        Show
        Sreekanth Ramakrishnan added a comment - Currently in trunk and .21 of hadoop, we have removed all the MiniMRCluster test to a new test case and TestQueueManager is plain unit test. All the integration tests have been moved to TestQueueManagerWithJobTracker which has only 3 test cases and all of the same runs under a minute even. Currently in latest build the same took only 30 seconds. This was done as part of MAPREDUCE-28 . Isn't solution at MAPREDUCE-28 sufficient?
        Dick King created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Dick King
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development