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

Hadoop daemons should not start up if the ownership/permissions on the directories used at runtime are misconfigured

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

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.22.0
    • 0.21.0
    • security
    • None
    • Reviewed

    Description

      The Hadoop daemons (like datanode, namenode) should refuse to start up if the ownership/permissions on directories they use at runtime are misconfigured or they are not as expected. For example, the local directory where the filesystem image is stored should be owned by the user running the namenode process and should be only readable by that user. We can provide this feature in common and HDFS and MapReduce can use the same.

      Attachments

        1. HADOOP-6566_yhadoop20.patch
          13 kB
          Arun Murthy
        2. HADOOP-6566_yhadoop20.patch
          11 kB
          Arun Murthy
        3. HADOOP-6566_yhadoop20.patch
          11 kB
          Arun Murthy
        4. HADOOP-6566_yhadoop20.patch
          11 kB
          Arun Murthy
        5. hadoop-6566-trunk-v1.patch
          6 kB
          Luke Lu
        6. hadoop-6566-trunk-v2.patch
          6 kB
          Luke Lu
        7. hadoop-6566-trunk-v3.patch
          14 kB
          Luke Lu
        8. hadoop-6566-trunk-v4.patch
          14 kB
          Luke Lu
        9. hadoop-6566-y20s-d1.patch
          3 kB
          Luke Lu

        Issue Links

        Activity

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

          People

            acmurthy Arun Murthy
            ddas Devaraj Das
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment