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

name server should log decisions that affect data: block creation, removal, replication

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.1.0
    • 0.2.0
    • None
    • None

    Description

      currently, there's no way to analyze and debug DFS errors where blocks disapear.
      name server should log its decisions that affect data, including block creation, removal, replication:

      • block <b> created, assigned to datanodes A, B, ...
      • datanode A dead, block <b> underreplicated(1), replicating to datanode C
      • datanode B dead, block <b> underreplicated(2), replicating to datanode D
      • datanode A alive, block <b> overreplicated, removing from datanode D
      • block <removed> from datanodes C, D, ...

      that will enable me to track down, two weeks later, a block that's missing from a file, and to debug the name server.

      extra credit:

      • rotate log file, as it might grow large
      • make this behaviour optional/configurable

      Attachments

        1. namenodeLogging.patch
          56 kB
          Hairong Kuang
        2. namenodeLogging.patch
          55 kB
          Hairong Kuang
        3. namenodeLogging.patch
          55 kB
          Hairong Kuang

        Activity

          People

            hairong Hairong Kuang
            yarnon Yoram Arnon
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: