Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 1 Aug 2012 03:42:35 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1761940218.124888.1343792555950.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <772110178.124799.1343789014791.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3746) Invalid counter tag in HDFS balancer
 which lead to infinite loop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eli Collins commented on HDFS-3746:
-----------------------------------

Why was this closed as fixed? There's no patch.
                
> Invalid counter tag in HDFS balancer which lead to infinite loop
> ----------------------------------------------------------------
>
>                 Key: HDFS-3746
>                 URL: https://issues.apache.org/jira/browse/HDFS-3746
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer
>    Affects Versions: 2.1.0-alpha, 3.0.0
>            Reporter: meng gong
>            Assignee: Jing Zhao
>              Labels: patch
>             Fix For: 2.1.0-alpha, 3.0.0
>
>
> Everytime banlancer try to move a block cross the rack. For every NameNodeConnector it will instance a new banlancer. The tag notChangedIterations is reseted to 0. Then it won't reach 5 and exit the thread for not moved in 5 consecutive iterations. This lead to a infinite loop

--
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