Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-dev@incubator.apache.org
Date: Fri, 14 Oct 2011 06:32:12 +0000 (UTC)
From: "Jakob Homan (Commented) (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: 
 <645583786.12870.1318573932535.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1578387723.12101.1318551372893.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GIRAPH-52) There should be a scheme to limit
 the counter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jakob Homan commented on GIRAPH-52:
-----------------------------------

That would be quite reasonable.  It could implement either of the schemes above (or a different one), or for non-limited clusters just churn out the counters.
                
> There should be a scheme to limit the counter
> ---------------------------------------------
>
>                 Key: GIRAPH-52
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-52
>             Project: Giraph
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.70.0
>            Reporter: Zhiwei Gu
>             Fix For: 0.70.0
>
>
> For hadoop version above 0.20.203.0., the cluster-wise configuration mapreduce.job.counters.limit cannot be overrided, while the superstep iterations is not deterministic, the job might run several hundreds or even thousand of supersteps, it will always kill the job. This will limit the usage of Giraph and is tooooo bad.

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