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

Posted to commits@samza.apache.org by "Jagadish (JIRA)" <ji...@apache.org> on 2017/03/11 15:00:07 UTC

[jira] [Updated] (SAMZA-1112) BrokerProxy does not log fatal errors

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

Jagadish updated SAMZA-1112:
----------------------------
    Fix Version/s: 0.13.0

Thanks for the contribution. Merged, and submitted. Fix version: 0.13.0. 

> BrokerProxy does not log fatal errors
> -------------------------------------
>
>                 Key: SAMZA-1112
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1112
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Tommy Becker
>            Assignee: Tommy Becker
>             Fix For: 0.13.0
>
>
> We hit an issue today where having a large backlog of messages to process caused an OutOfMemoryError in one our our jobs, presumably due to the BrokerProxy's default buffer size of 50k messages being too large. The issue though was that the error was not logged, and from the logs it appeared that the job just spontaneously exited. 
> Looking at the BrokerProxy, there is no UncaughtExceptionHandler set for its thread, so any fatal errors only go to stderr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)