hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13356) Balancer:Set default value of minBlockSize to 10mb
Date Mon, 23 Apr 2018 23:11:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449013#comment-16449013
] 

Hudson commented on HDFS-13356:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #14052 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14052/])
HDFS-13356. Balancer:Set default value of minBlockSize to 10mb. (bharat: rev 9b5375e0c1ee8c634a5accb7415ec27440543a60)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/proto/NamenodeProtocol.proto


> Balancer:Set default value of minBlockSize to 10mb 
> ---------------------------------------------------
>
>                 Key: HDFS-13356
>                 URL: https://issues.apache.org/jira/browse/HDFS-13356
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer &amp; mover
>    Affects Versions: 2.7.5
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: balancer, upgrades
>         Attachments: HDFS-13356.00.patch, HDFS-13356.01.patch, HDFS-13356.02.patch
>
>
>  It seems we can run into a problem while a rolling upgrade with this.
> The Balancer is upgraded after NameNodes, so once NN is upgraded it will expect {{minBlockSize}}
parameter in {{getBlocks()}}. The Balancer cannot send it yet, so NN will use the default,
which you set to 0. So NN will start unexpectedly sending small blocks to the Balancer. So
we should
>  # either change the default in protobuf to 10 MB
>  # or treat {{minBlockSize == 0}} in {{NameNodeRpcServer}} as a signal to use the
configuration variable {{DFSConfigKeys.DFS_BALANCER_GETBLOCKS_MIN_BLOCK_SIZE_KEY}}.
> If you agree, we should create a follow up jira. I wanted to backport this down the chain
of branches, but this upgrade scenario is stopping me.
> [~shv] commented this in  HDFS-13222 jira.
> https://issues.apache.org/jira/browse/HDFS-13222?focusedCommentId=16414855&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16414855



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message