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

Posted to commits@samza.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2016/02/19 01:49:18 UTC

[jira] [Created] (SAMZA-877) ThreadJobFactory doesn't need JobCoordinator service running

Boris Shkolnik created SAMZA-877:
------------------------------------

             Summary: ThreadJobFactory doesn't need JobCoordinator service running
                 Key: SAMZA-877
                 URL: https://issues.apache.org/jira/browse/SAMZA-877
             Project: Samza
          Issue Type: Bug
            Reporter: Boris Shkolnik
            Assignee: Boris Shkolnik


currently it starts the JobCoordinator server, starts the job, and stops the JobCoordinator server right away. There is not need for a separate server here, because the job model is passed directly to the container. And if container dies it is not going to be restarted anyway.

It seems that we can just disable both start and stop of JobCoordinator in ThreadJobCoordinator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)