You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hung Tran (JIRA)" <ji...@apache.org> on 2019/03/26 00:14:00 UTC
[jira] [Resolved] (GOBBLIN-703) Allow planning job to be run in a
non-blocking way
[ https://issues.apache.org/jira/browse/GOBBLIN-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hung Tran resolved GOBBLIN-703.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.15.0
Issue resolved by pull request #2573
[https://github.com/apache/incubator-gobblin/pull/2573]
> Allow planning job to be run in a non-blocking way
> --------------------------------------------------
>
> Key: GOBBLIN-703
> URL: https://issues.apache.org/jira/browse/GOBBLIN-703
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Kuai Yu
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Today all the planning job will be running in a dedicated thread pool and will wait until the full execution to be completed. This requires a lot of system resources and a dedicated monitoring thread. The improvement here is to reduce the waiting time on a dedicated monitoring thread. Basically once the planning job submits to the Helix, we don't need to wait on the job completion. The job status monitoring will be achieved by GaaS monitoring.
> By doing this, we are freeing most of the threadpool resources because each monitoring thread will be immediately return after it finishes the job submission.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)