Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Wed, 28 May 2014 20:07:01 +0000 (UTC)
From: "Sergey Edunov (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12717116.1401307084826.33637.1401307621674@arcas>
In-Reply-To: <JIRA.12717116.1401307084826@arcas>
References: <JIRA.12717116.1401307084826@arcas>
Subject: [jira] [Commented] (GIRAPH-903) Detect crashes of Netty threads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sergey Edunov commented on GIRAPH-903:
--------------------------------------

CR: https://reviews.apache.org/r/21987/ 

> Detect crashes of Netty threads
> -------------------------------
>
>                 Key: GIRAPH-903
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-903
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Sergey Edunov
>            Priority: Minor
>         Attachments: GIRAPH-903.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When some of the request processing threads fails, the worker gets stuck but the job doesn't fail and it has to be killed manually. We should detect netty thread crashes and fail the job automatically.
> You can easily reproduce this if you add a mistake to deserialization of messages for example.


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