[GOBBLIN-510] Decouple JobExecutionLauncher and JobExecutionDriver

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Assignee: Kuai Yu
• Reporter: Kuai Yu
• Created: 06/Jun/18 18:08
• Updated: 07/Jun/18 18:22
• Resolved: 07/Jun/18 18:22

Description

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.