You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Abhishek Shivanna (Jira)" <ji...@apache.org> on 2019/12/21 02:25:00 UTC

[jira] [Resolved] (SAMZA-2423) Heartbeat failure leads the to container shutdown with exit code 0

     [ https://issues.apache.org/jira/browse/SAMZA-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Shivanna resolved SAMZA-2423.
--------------------------------------
    Resolution: Fixed

> Heartbeat failure leads the to container shutdown with exit code 0
> ------------------------------------------------------------------
>
>                 Key: SAMZA-2423
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2423
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Abhishek Shivanna
>            Assignee: Abhishek Shivanna
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Background: A Samza container periodically calls the AM through a HeartbeatMonitor while the container is running. If a container can't contact the AM because of a network issue or the AM moved hosts, the container will shutdown afterwards and is expected to restart afterwards.
> The issue is that the current code (ContainerLaunchUntil.java) returns with a status exit code of 0 leading the job coordinator to not reschedule the container.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)