Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-12323

NameNode terminates after full GC thinking QJM unresponsive if full GC is much longer than timeout

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      HDFS-10733 attempted to fix the issue where the Namenode process would terminate itself if it had a GC pause which lasted longer than the QJM timeout, since it would think that the QJM had taken too long to respond. However, it only bumps up the timeout expiration by one timeout length, so if the GC pause was e.g. 2x the length of the timeout, a TimeoutException will be thrown and the NN will still terminate itself.

      Thanks to Jiandan Yang for noting this issue as a comment on HDFS-10733; we have also seen this issue on a real cluster even after HDFS-10733 is applied.

        Attachments

        1. HDFS-12323.004.patch
          7 kB
          Erik Krogen
        2. HDFS-12323.003.patch
          7 kB
          Erik Krogen
        3. HDFS-12323.002.patch
          7 kB
          Erik Krogen
        4. HDFS-12323.001.patch
          7 kB
          Erik Krogen
        5. HDFS-12323.000.patch
          3 kB
          Erik Krogen

          Issue Links

            Activity

              People

              • Assignee:
                xkrogen Erik Krogen
                Reporter:
                xkrogen Erik Krogen
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: