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

Balancer should not use property dfs.datanode.balance.max.concurrent.moves

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 2.6.0
    • None
    • balancer & mover

    Description

      It is very confusing for both Balancer and Datanode to use the same property dfs.datanode.balance.max.concurrent.moves. It is especially so for the Balancer because the property has "datanode" in the name string. Many customers forget to set the property for the Balancer.

      Change the Balancer to use a new property dfs.balancer.max.concurrent.moves.

      Attachments

        Issue Links

          is depended upon by

          Sub-task - The sub-task of the issue HDFS-10294 Balancer configures DN properties

          • Major - Major loss of function.
          • Open
          relates to

          Sub-task - The sub-task of the issue HDFS-7466 Allow different values for dfs.datanode.balance.max.concurrent.moves per datanode

          • Major - Major loss of function.
          • In Progress

          Improvement - An improvement or enhancement to an existing feature or task. HDFS-10289 Balancer configures DNs directly

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Activity

            People

              jzhuge John Zhuge
              jzhuge John Zhuge
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated: