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

JVM should not be killed but given an opportunity to exit gracefully

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.19.0
    • Fix Version/s: 0.20.0
    • Component/s: None
    • Labels:
      None
    • Release Note:
      Hide
      This patch (1) Adds a shutdownHook that does syncLogs sothat logs of the current task are flushed and log.index is up to date in cases like System.exit(), or killed using signals(other than SIGKILL).
      (2) Changes writeToIndexFile() to write to a temporary index file first and then rename to log.index sothat updates to log.index file are atomic.
      Show
      This patch (1) Adds a shutdownHook that does syncLogs sothat logs of the current task are flushed and log.index is up to date in cases like System.exit(), or killed using signals(other than SIGKILL). (2) Changes writeToIndexFile() to write to a temporary index file first and then rename to log.index sothat updates to log.index file are atomic.

      Description

      When the tasktracker picks an idle JVM for purging, it should signal the JVM to exit gracefully, rather than forcefully killing it. This might have the unfortunate side effect of logs not fully flushed yet in some cases.

        Attachments

        1. HADOOP-4374.patch
          9 kB
          Ravi Gummadi
        2. HADOOP-4374.v1.1.patch
          9 kB
          Ravi Gummadi
        3. HADOOP-4374.v1.2.patch
          9 kB
          Ravi Gummadi
        4. HADOOP-4374.v1.patch
          9 kB
          Ravi Gummadi

          Activity

            People

            • Assignee:
              ravidotg Ravi Gummadi
              Reporter:
              devaraj Devaraj Das
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: