giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-871) Map task jvm never exits since netty 4 upgrade
Date Sat, 22 Mar 2014 01:22:43 GMT

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

Hudson commented on GIRAPH-871:
-------------------------------

ABORTED: Integrated in Giraph-trunk-Commit #1433 (See [https://builds.apache.org/job/Giraph-trunk-Commit/1433/])
GIRAPH-871 (claudio: http://git-wip-us.apache.org/repos/asf/?p=giraph.git&a=commit&h=dcbb4805887fa5dc2e3fb21c8a6769aa4172c986)
* CHANGELOG
* giraph-core/src/main/java/org/apache/giraph/comm/netty/NettyClient.java


> Map task jvm never exits since netty 4 upgrade
> ----------------------------------------------
>
>                 Key: GIRAPH-871
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-871
>             Project: Giraph
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 1.1.0
>            Reporter: Craig Muchinsky
>             Fix For: 1.1.0
>
>         Attachments: GIRAPH-871.patch
>
>
> Some changes made to the NettyClient.stop() logic related to netty 4 are causing the
final worker thread to hang up indefinitely, preventing the map task jvm from exiting. In
particular, the call to ProgressableUtils.awaitTerminationFuture() is blocking inside the
ChannelFutureListener callback and deadlocking. Simply moving the ProgressableUtils.awaitTerminationFuture()
calls outside of the ChannelFutureListener callback and placing them at the end of the NettyClient.stop()
method seems to cure the problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message