giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Reisman (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-304) Closed channels between workers
Date Mon, 20 Aug 2012 19:41:38 GMT


Eli Reisman commented on GIRAPH-304:

After running jobs all weekend I am reluctantly thinking perhaps we need to raise the default
thread pool max from 32 a little higher again (maybe not 64 but 48 or something?) because
when the resources are available the higher limit seems to give us a bit more headroom before
a worker's Netty impl crashes. Just an observation based on playing with it, not sure if there's
a better fix to go with the symptoms. But thought I'd throw it out there.

> Closed channels between workers
> -------------------------------
>                 Key: GIRAPH-304
>                 URL:
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Alessandro Presta
>            Assignee: Alessandro Presta
>         Attachments: GIRAPH-304.patch
> With GIRAPH-300 we are able to complete jobs with higher numbers of workers thanks to
retrying failed connections. However, we still observe ClosedChannelException with more than
a 100 workers.
> The patch also introduces a default TCP backlog of 100, so we should probably set this
dynamically to equal the number of workers instead.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message