Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-4508

Two minor improvements to the QJM Deployment docs

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0.3-alpha
    • Fix Version/s: None
    • Component/s: documentation
    • Labels:
      None

      Description

      Suggested by ML user Azurry, the docs at http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/HDFSHighAvailabilityWithQJM.html#Deployment_details can be improved for two specific lines:

      • If you have already formatted the NameNode, or are converting a non-HA-enabled cluster to be HA-enabled, you should now copy over the contents of your NameNode metadata directories to the other, unformatted NameNode by running the command "hdfs namenode -bootstrapStandby" on the unformatted NameNode. Running this command will also ensure that the JournalNodes (as configured by dfs.namenode.shared.edits.dir) contain sufficient edits transactions to be able to start both NameNodes.
      • If you are converting a non-HA NameNode to be HA, you should run the command "hdfs -initializeSharedEdits", which will initialize the JournalNodes with the edits data from the local NameNode edits directories.
      1. HDFS-4508.patch
        2 kB
        Daisuke Kobayashi

        Activity

        Harsh J created issue -
        Hide
        Harsh J added a comment -

        Improved text must be:

        • If you have already formatted the NameNode, or are converting a non-HA-enabled cluster to be HA-enabled, you should now copy over the contents of your NameNode metadata directories to the other, unformatted NameNode by running the command "hdfs namenode -bootstrapStandby" on the unformatted NameNode. Running this command needs the formatted NameNode to be up and functional, and will also ensure that the JournalNodes (as configured by dfs.namenode.shared.edits.dir) contain sufficient edits transactions to be able to start the new NameNode.
        • If you are converting a non-HA NameNode to be HA, you should run the command "hdfs namenode -initializeSharedEdits", which will initialize the JournalNodes with the edits data from the local NameNode edits directories.
        Show
        Harsh J added a comment - Improved text must be: If you have already formatted the NameNode, or are converting a non-HA-enabled cluster to be HA-enabled, you should now copy over the contents of your NameNode metadata directories to the other, unformatted NameNode by running the command "hdfs namenode -bootstrapStandby" on the unformatted NameNode. Running this command needs the formatted NameNode to be up and functional, and will also ensure that the JournalNodes (as configured by dfs.namenode.shared.edits.dir) contain sufficient edits transactions to be able to start the new NameNode. If you are converting a non-HA NameNode to be HA, you should run the command "hdfs namenode -initializeSharedEdits", which will initialize the JournalNodes with the edits data from the local NameNode edits directories.
        Daisuke Kobayashi made changes -
        Field Original Value New Value
        Assignee Daisuke Kobayashi [ daisuke.kobayashi ]
        Hide
        Daisuke Kobayashi added a comment -

        modified.

        Show
        Daisuke Kobayashi added a comment - modified.
        Daisuke Kobayashi made changes -
        Attachment HDFS-4508.patch [ 12570308 ]

          People

          • Assignee:
            Daisuke Kobayashi
            Reporter:
            Harsh J
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development