Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-4967

Inconsistent state in JVM manager

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.19.1
    • None
    • None
    • Reviewed

    Description

      The following is the scenario:
      -> TT got a LaunchTaskAction. And It found the slot free. It started the TaskRunner
      -> TT received KillJobActtion. It did a runner.kill().
      But, runner.kill() didn't remove JVM Runner from jvmIdToRunner , as it is not polulated yet.
      It released the slots.
      -> TaskRunner thread spawned jvm and populated jvmIdToRunner.
      -> The next task getting launched on the slot finds it as busy.

      Attachments

        1. 4967.patch
          2 kB
          Devaraj Das

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ddas Devaraj Das
            amareshwari Amareshwari Sriramadasu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment