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

HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.14.1
    • Fix Version/s: 0.15.0
    • Component/s: None
    • Labels:
      None

      Description

      For the security purpose, it is nice to have a NamenodeProtocol to allow secondary namenodes and rebalacing processes to communicate with a primary namenode. In the first version the NamenodeProtocol is going to support one RPC:
      BlockLocations[] getBlocks(DatanodeID datanode, long size);
      This RPC allows a rebalancing process to fetch a partial blocks map from a namenode. It returns a list of blocks on the given datanode and its locations, whose total size is the given size.

        Attachments

        1. namenodeProtocol.patch
          14 kB
          Hairong Kuang
        2. namenodeProtocol1.patch
          17 kB
          Hairong Kuang
        3. namenodeProtocol2.patch
          17 kB
          Hairong Kuang
        4. namenodeProtocol3.patch
          17 kB
          Hairong Kuang

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              hairong Hairong Kuang Assign to me
              Reporter:
              hairong Hairong Kuang

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment