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

Use ERROR instead of INFO for volume failure logs

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

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-alpha
    • Fix Version/s: 2.0.3-alpha
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      I misconfigured the permissions of the DataNode data directories (they were owned by root, instead of hdfs).

      I wasn't aware of this misconfiguration until a few days later. I usually search through the logs for WARN and ERROR but didn't find messages at these levels that indicated volume failure.

      After more carefully reading the logs, I found:

      2012-10-01 13:07:10,440 INFO org.apache.hadoop.hdfs.server.common.Storage: Cannot access storage directory /data/4/dfs/dn
      2012-10-01 13:07:10,440 INFO org.apache.hadoop.hdfs.server.common.Storage: Storage directory /data/4/dfs/dn does not exist.
      

      I think we should bump the log level to ERROR. This will make the problem more visible to users.

        Attachments

        1. HDFS-4048.patch.trunk
          2 kB
          Stephen Chu
        2. HDFS-4048.patch.branch-2
          2 kB
          Stephen Chu
        3. HDFS-4048.patch.branch-2.2
          3 kB
          Stephen Chu
        4. HDFS-4048.patch.trunk.2
          3 kB
          Stephen Chu
        5. HDFS-4048.patch.trunk.3
          3 kB
          Stephen Chu

          Activity

            People

            • Assignee:
              schu Stephen Chu
              Reporter:
              schu Stephen Chu

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment