giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GIRAPH-140) Enforce a maximum number of iterations
Date Fri, 29 Mar 2013 06:13:16 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Avery Ching resolved GIRAPH-140.
--------------------------------

    Resolution: Duplicate

I think so.  Closing.
                
> Enforce a maximum number of iterations
> --------------------------------------
>
>                 Key: GIRAPH-140
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-140
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Jakob Homan
>
> While Giraph is still on MR and keeping track of its statistics via Hadoop's counters,
there is the danger that a huge number of iterations will negatively impact the cluster's
jobtracker by adding counter statistics for each one (basically, the flip side of GIRAPH-52).
 We should have a configurable maximum number of iterations to prevent this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message