Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-4413

Secondary namenode won't start if HDFS isn't the default file system

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1-win, 1.2.1
    • Fix Version/s: 1.2.0
    • Component/s: namenode
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      If HDFS is not the default file system (fs.default.name is something other than hdfs://...), then secondary namenode throws early on in its initialization. This is a needless check as far as I can tell, and blocks scenarios where HDFS services are up but HDFS is not the default file system.

      1. HDFS-4413.branch-1.patch
        0.8 kB
        Mostafa Elhemali

        Activity

        Mostafa Elhemali created issue -
        Mostafa Elhemali made changes -
        Field Original Value New Value
        Attachment HDFS-4413.branch-1.patch [ 12565225 ]
        Chris Nauroth made changes -
        Assignee Mostafa Elhemali [ mostafae ]
        Affects Version/s 1-win [ 12320362 ]
        Affects Version/s 1.2.1 [ 12324148 ]
        Target Version/s 1-win, 1.2.1 [ 12320362, 12324148 ]
        Component/s namenode [ 12312926 ]
        Suresh Srinivas made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Hadoop Flags Reviewed [ 10343 ]
        Fix Version/s 1.2.0 [ 12321657 ]
        Resolution Fixed [ 1 ]
        Matt Foley made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Matt Foley made changes -
        Target Version/s 1-win, 1.2.1 [ 12320362, 12324148 ] 1.2.0, 1-win [ 12321657, 12320362 ]

          People

          • Assignee:
            Mostafa Elhemali
            Reporter:
            Mostafa Elhemali
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development