Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-877

ThreadJobFactory doesn't need JobCoordinator service running

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            boryas Boris Shkolnik
            boryas Boris Shkolnik

            Dates

              Created:
              Updated:

              Slack

                Issue deployment