hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3295) Mismatch in number of bytes already moved and number of bytes being moved in balancer report
Date Wed, 01 Aug 2012 11:03:03 GMT

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

Uma Maheswara Rao G commented on HDFS-3295:
-------------------------------------------

Thanks a lot, Junping, for taking a look and Also thanks to Meng for reporting the issue in
other JIRA.

I think currently Balancer will shutdown its executor pools in run method itself once it balanced.
So, when we reuse the same balancer, it will fail to use the executor pools as they got shutdown
as part of previous run. 

May be the other option is to add the shutdown method in balancer and lets iterate for all
the nnConnectors and shutdown the corresponding Balancer? So, the executors can be used when
we reuse the balancer object with the nnConnectors.
Ashish, what do you think about this?
                
> Mismatch in number of bytes already moved and number of bytes being moved in balancer
report
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3295
>                 URL: https://issues.apache.org/jira/browse/HDFS-3295
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer
>    Affects Versions: 0.23.0
>            Reporter: J.Andreina
>            Assignee: Ashish Singhi
>             Fix For: 0.24.0
>
>         Attachments: HDFS-3295.patch, HDFS-3295.patch, HDFS-3295.patch, HDFS-3295.patch,
HDFS-3295.patch
>
>
> Scenario:
> Replication factor = 1,fs.defaultFS=hdfs://namenodeip:port,dfs.namenode.rpc-address=namenodeip:port.
> step 1: started DN1.Pumped 4.67GB of data
> step 2: started DN2.
> step 3: issued the balancer cmd(./start-balancer.sh -threshold 1)
> Totally  848.41 MB  has been moved to 2DN and took 4 iterations to move the blocks to
2DN.
> But in balancer output in all the iterations the number of bytes already moved is alway
0KB  and there is mismatch in the Bytes being moved with the bytes left to move
> Balancer output for 2nd Iteration
> =================================
> {noformat}
> Time Stamp               Iteration#  Bytes Already Moved  Bytes Left To Move  Bytes Being
Moved
> Apr 18, 2012 12:41:20 PM          0                 0 KB           848.41 MB        
 151.18 MB
> Apr 18, 2012 1:06:46 PM           1                 0 KB           646.02 MB        
 151.18 MB
> Apr 18, 2012 1:10:28 PM           2                 0 KB           417.43 MB        
 151.18 MB
> Apr 18, 2012 1:14:04 PM           3                 0 KB           223.84 MB        
 151.18 MB
> Apr 18, 2012 1:18:10 PM           4                 0 KB            30.34 MB        
 151.18 MB{noformat}
> In the above balancer output
> •Bytes already moved is 0KB
> • In 3 rd iterarion Bytes left to move is 223.84 MB but Bytes being moved is 151.18
MB . So in next iteration the bytes left to move should be 223.84 MB - 151.18 MB 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message