You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/06/28 18:10:00 UTC

[jira] [Resolved] (SAMZA-1340) StreamProcessor does not propagate container failures from StreamTask

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

Navina Ramesh resolved SAMZA-1340.
----------------------------------
    Resolution: Fixed

Issue resolved by pull request 230
[https://github.com/apache/samza/pull/230]

> StreamProcessor does not propagate container failures from StreamTask
> ---------------------------------------------------------------------
>
>                 Key: SAMZA-1340
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1340
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.131
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>             Fix For: 0.13.1
>
>
> Based on [~cpettitt]'s observation:
> bq. I'm on Samza's master branch. If my task throws from one of its operators I get back a success state from the LocalApplicationRunner.
> bq. The root cause appears to be in SamzaContainerListener#onContainerFailed in StreamProcessor. There we call a regular stop and have not recorded anywhere that an exception was raised. Consequently onCoordinatorStop is invoked and the processorListener gets its onShutdown callback called instead of onFailure via onCoordinatorFailure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)