Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-14603 Über-JIRA: HDFS RBF stabilization phase II
  3. HDFS-13248

RBF: Namenode need to choose block location for the client

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      When execute a put operation via router, the NameNode will choose block location for the router, not for the real client. This will affect the file's locality.

      I think on both NameNode and Router, we should add a new addBlock method, or add a parameter for the current addBlock method, to pass the real client information.

      Attachments

        1. debug-info-1.jpeg
          266 kB
          Wu Weiwei
        2. debug-info-2.jpeg
          242 kB
          Wu Weiwei
        3. clientMachine-call-path.jpeg
          171 kB
          Wu Weiwei
        4. HDFS-13248.000.patch
          6 kB
          Íñigo Goiri
        5. HDFS-13248.001.patch
          8 kB
          Íñigo Goiri
        6. HDFS-13248.002.patch
          4 kB
          Hui Fei
        7. HDFS-13248.003.patch
          8 kB
          Hui Fei
        8. HDFS-13248.004.patch
          9 kB
          Hui Fei
        9. HDFS-13248.005.patch
          9 kB
          Hui Fei
        10. HDFS-Router-Data-Locality.odt
          26 kB
          Ayush Saxena
        11. RBF Data Locality Design.pdf
          91 kB
          Xiaoqiao He

        Issue Links

        Activity

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

          People

            omalley Owen O'Malley Assign to me
            wuweiwei Wu Weiwei
            Votes:
            0 Vote for this issue
            Watchers:
            22 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 5h 10m
              5h 10m

              Slack

                Issue deployment