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

Posted to dev@gobblin.apache.org by "Kuai Yu (JIRA)" <ji...@apache.org> on 2018/06/06 18:09:00 UTC

[jira] [Created] (GOBBLIN-510) Decouple JobExecutionLauncher and JobExecutionDriver

Kuai Yu created GOBBLIN-510:
-------------------------------

             Summary: Decouple JobExecutionLauncher and JobExecutionDriver
                 Key: GOBBLIN-510
                 URL: https://issues.apache.org/jira/browse/GOBBLIN-510
             Project: Apache Gobblin
          Issue Type: New Feature
            Reporter: Kuai Yu
            Assignee: Kuai Yu


Today JobExecutionLauncher and JobExecutionDriver is coupled. It means when JobExecutionLauncher invokes launchJob, a JobExecutionDriver is immediately return. This is not good for gobblin cluster because the Launcher might running in manager node but the actual driver logic is running on worker node. We need some refactoring to allow us decouple these two.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)