You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Xinyu Liu (JIRA)" <ji...@apache.org> on 2018/01/04 20:31:00 UTC

[jira] [Updated] (SAMZA-1455) Shutdown coordinator stream producers and consumers cleanly in JobRunner

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

Xinyu Liu updated SAMZA-1455:
-----------------------------
    Fix Version/s: 0.15.0

> Shutdown coordinator stream producers and consumers cleanly in JobRunner
> ------------------------------------------------------------------------
>
>                 Key: SAMZA-1455
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1455
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jagadish
>             Fix For: 0.15.0
>
>
> Currently, we do not cleanly close the producer and consumer in the JobRunner. This means that, any exception happening in the JobRunner will simply exit the main thread but not call tear-down the producers/consumers. For producers and consumers that spawn non-daemon threads (for example, a KafkaConsumer), this has the effect of not shutting down the JVM cleanly. 
> In our production clusters, We have observed that JVM processes (corresponding to the JobRunner) do not shut-down. Often, these processes hold on to deleted file handles leading to multiple resource leaks.



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