Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-14795

Add Throttler for writing block

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      DataXceiver#writeBlock

      blockReceiver.receiveBlock(mirrorOut, mirrorIn, replyOut,
                  mirrorAddr, null, targets, false);
      

      As above code, DataXceiver#writeBlock doesn't throttler.
      I think it is necessary to throttle for writing block, while add throttler in stage of PIPELINE_SETUP_APPEND_RECOVERY or PIPELINE_SETUP_STREAMING_RECOVERY.

      Default throttler value is still null.

        Attachments

        1. HDFS-14795.012.patch
          11 kB
          Lisheng Sun
        2. HDFS-14795.011.patch
          9 kB
          Lisheng Sun
        3. HDFS-14795.010.patch
          9 kB
          Lisheng Sun
        4. HDFS-14795.009.patch
          9 kB
          Lisheng Sun
        5. HDFS-14795.008.patch
          9 kB
          Lisheng Sun
        6. HDFS-14795.007.patch
          9 kB
          Lisheng Sun
        7. HDFS-14795.006.patch
          9 kB
          Lisheng Sun
        8. HDFS-14795.005.patch
          8 kB
          Lisheng Sun
        9. HDFS-14795.004.patch
          8 kB
          Lisheng Sun
        10. HDFS-14795.003.patch
          8 kB
          Lisheng Sun
        11. HDFS-14795.002.patch
          6 kB
          Lisheng Sun
        12. HDFS-14795.001.patch
          6 kB
          Lisheng Sun

        Issue Links

          Activity

            People

            • Assignee:
              leosun08 Lisheng Sun
              Reporter:
              leosun08 Lisheng Sun

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment