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/03/07 23:45:38 UTC

[jira] [Commented] (SAMZA-1125) Container.shutdown() only stops the runloop

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

Navina Ramesh commented on SAMZA-1125:
--------------------------------------

[~xinyu] Isn't Runnable.run a blocking call in the current thread ?? Ideally speaking, once runloop exits, it should invoke the shutdown sequence. Am I missing something ? 

> Container.shutdown() only stops the runloop
> -------------------------------------------
>
>                 Key: SAMZA-1125
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1125
>             Project: Samza
>          Issue Type: New Feature
>            Reporter: Xinyu Liu
>            Assignee: Navina Ramesh
>
> Currently SamzaContainer.shutdown() only stops the RunLoop. Seems to me all the dependencies used by the container are not properly shutdown. E.g. the kafka system consumer/producer will not be shut down. In standalone case (ZkJobCoordinator.java), the next time controller.startContainer() will create the container with all these dependencies again. The Kafka producers/consumers will be created again without closing the previous ones. Please verify this is a problem and needs to be fixed.



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