Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-7327

Job.waitForCompletion function can sleep most for 596 hours when jobclient.completion.poll.interval is misconfigured , causing the job to hang

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.3.0
    • Fix Version/s: None
    • Component/s: client
    • Labels:
      None

      Description

      The loop terminates depending on a configurable value and there is little sanity checking on this value. When jobclient.completion.poll.interval is misconfigured to INT_MAX, it can cause the loop to sleep at most for 596 hours. The thread would get stuck and never return to the user even if the job completes. We suggest adding a cap value or a warning message.

      public boolean waitForCompletion(boolean verbose
                                         ) throws IOException, InterruptedException,
                                                  ClassNotFoundException {
      ... 
         while (!isComplete()) {
              try {
                  Thread.sleep(completionPollIntervalMillis);
              } catch (InterruptedException ie) {
          }
      ...
      }
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tshan Tina Shan

              Dates

              • Created:
                Updated:

                Issue deployment