[jira] [Commented] (GIRAPH-36) Ensure that subclassing BasicVertex is possible by user apps
[ https://issues.apache.org/jira/browse/GIRAPH-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13126432#comment-13126432 ] Claudio Martella commented on GIRAPH-36: Hey Jake, did you get any chance to fix this one lately? This is quite blocking for me, I'm based on BasicVertex. Can I help out somehow? Ensure that subclassing BasicVertex is possible by user apps Key: GIRAPH-36 URL: https://issues.apache.org/jira/browse/GIRAPH-36 Project: Giraph Issue Type: Improvement Components: graph Affects Versions: 0.70.0 Reporter: Jake Mannix Assignee: Jake Mannix Priority: Blocker Fix For: 0.70.0 Original assumptions in Giraph were that all users would subclass Vertex (which extended MutableVertex extended BasicVertex). Classes which wish to have application specific data structures (ie. not a TreeMapI, EdgeI,E) may need to extend either MutableVertex or BasicVertex. Unfortunately VertexRange extends ArrayListVertex, and there are other places where the assumption is that vertex classes are either Vertex, or at least MutableVertex. Let's make sure the internal APIs allow for BasicVertex to be the base class. -- 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
[jira] [Created] (GIRAPH-52) There should be a scheme to limit the counter
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 to 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
[jira] [Commented] (GIRAPH-52) There should be a scheme to limit the counter
[ https://issues.apache.org/jira/browse/GIRAPH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127169#comment-13127169 ] Avery Ching commented on GIRAPH-52: --- Here's a related issue https://issues.apache.org/jira/browse/GIRAPH-43. 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 to 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
[jira] [Commented] (GIRAPH-52) There should be a scheme to limit the counter
[ https://issues.apache.org/jira/browse/GIRAPH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127234#comment-13127234 ] Zhiwei Gu commented on GIRAPH-52: - yeah, but it is resolved as not to fix. Can I reopen it as it is a blocker for me? 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 to 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
[jira] [Commented] (GIRAPH-52) There should be a scheme to limit the counter
[ https://issues.apache.org/jira/browse/GIRAPH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127235#comment-13127235 ] Jakob Homan commented on GIRAPH-52: --- If you'd like to come up with a way around the limit, this would be the correct JIRA. Perhaps just output statistics for the last n iterations? Or every m iteration, skipping enough to stay under the limit? One could check for the presence of the conf value with reasonable certainty that if it's not there this behavior would be appropriate (this isn't full proof since the value could be set on the server but not the client, but this would work 99% of the time and an error message, if it doesn't, could suggest that possibility). 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 to 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
[jira] [Commented] (GIRAPH-52) There should be a scheme to limit the counter
[ https://issues.apache.org/jira/browse/GIRAPH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127239#comment-13127239 ] Jakob Homan commented on GIRAPH-52: --- above, last as in final, not previous. 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 to 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
