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

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.22.0
    • Fix Version/s: 0.21.0
    • Component/s: security
    • Labels:
      None
    • Hadoop Flags:
      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.

      1. HADOOP-6566_yhadoop20.patch
        13 kB
        Arun C Murthy
      2. HADOOP-6566_yhadoop20.patch
        11 kB
        Arun C Murthy
      3. HADOOP-6566_yhadoop20.patch
        11 kB
        Arun C Murthy
      4. HADOOP-6566_yhadoop20.patch
        11 kB
        Arun C 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

          Eli Collins made changes -
          Link This issue is related to HDFS-2117 [ HDFS-2117 ]
          Harsh J made changes -
          Link This issue is duplicated by HADOOP-7431 [ HADOOP-7431 ]
          Tom White made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Tom White made changes -
          Fix Version/s 0.21.0 [ 12313563 ]
          Fix Version/s 0.22.0 [ 12314296 ]
          Chris Douglas made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Hadoop Flags [Reviewed]
          Resolution Fixed [ 1 ]
          Chris Douglas made changes -
          Link This issue is blocked by HDFS-997 [ HDFS-997 ]
          Chris Douglas made changes -
          Link This issue blocks HDFS-997 [ HDFS-997 ]
          Luke Lu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Hadoop Flags [Incompatible change]
          Luke Lu made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Luke Lu made changes -
          Attachment hadoop-6566-trunk-v4.patch [ 12439073 ]
          Luke Lu made changes -
          Attachment hadoop-6566-y20s-d1.patch [ 12439072 ]
          Luke Lu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Luke Lu made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Luke Lu made changes -
          Attachment hadoop-6566-trunk-v3.patch [ 12438852 ]
          Chris Douglas made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Chris Douglas made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Luke Lu made changes -
          Attachment hadoop-6566-trunk-v2.patch [ 12438478 ]
          Luke Lu made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Hadoop Flags [Reviewed, Incompatible change] [Incompatible change]
          Affects Version/s 0.22.0 [ 12314296 ]
          Luke Lu made changes -
          Attachment hadoop-6566-trunk-v1.patch [ 12438346 ]
          Konstantin Boudnik made changes -
          Hadoop Flags [Reviewed] [Incompatible change, Reviewed]
          Tsz Wo Nicholas Sze made changes -
          Hadoop Flags [Reviewed]
          Arun C Murthy made changes -
          Attachment HADOOP-6566_yhadoop20.patch [ 12436814 ]
          Arun C Murthy made changes -
          Attachment HADOOP-6566_yhadoop20.patch [ 12436745 ]
          Arun C Murthy made changes -
          Attachment HADOOP-6566_yhadoop20.patch [ 12436740 ]
          Arun C Murthy made changes -
          Attachment HADOOP-6566_yhadoop20.patch [ 12436687 ]
          Arun C Murthy made changes -
          Assignee Arun C Murthy [ acmurthy ]
          Arun C Murthy made changes -
          Link This issue is blocked by HDFS-997 [ HDFS-997 ]
          Devaraj Das made changes -
          Field Original Value New Value
          Description The Hadoop daemons (like datanode, namenode) should refuse to start up if the ownership/permissions 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. 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.
          Devaraj Das created issue -

            People

            • Assignee:
              Arun C Murthy
              Reporter:
              Devaraj Das
            • Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development