[
https://issues.apache.org/jira/browse/GIRAPH-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430632#comment-13430632
]
Hudson commented on GIRAPH-287:
-------------------------------
Integrated in Giraph-trunk-Commit #162 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/162/])
GIRAPH-287. Add option to limit the number of open requests. Contributed by
Maja Kabiljo. (Revision 1370522)
Result = SUCCESS
jghoman :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1370522
Files :
* /giraph/trunk/CHANGELOG
* /giraph/trunk/src/main/java/org/apache/giraph/comm/NettyClient.java
> Add option to limit the number of open requests
> -----------------------------------------------
>
> Key: GIRAPH-287
> URL: https://issues.apache.org/jira/browse/GIRAPH-287
> Project: Giraph
> Issue Type: Improvement
> Affects Versions: 0.2.0
> Reporter: Maja Kabiljo
> Assignee: Maja Kabiljo
> Fix For: 0.2.0
>
> Attachments: GIRAPH-287-2.patch, GIRAPH-287.patch
>
>
> As I mentioned in the discussion on the mailing list, GIRAPH-45 patch itself
> wasn't enough to run jobs with any amount of messages data. The thing which
> can still happen is that we have too many send messages requests to which we
> didn't get replies yet, so these requests use all our memory. Adding limit on
> the number of open requests will fix that last case.
--
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
