[
https://issues.apache.org/jira/browse/GOBBLIN-703?focusedWorklogId=215714&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-215714
]
ASF GitHub Bot logged work on GOBBLIN-703:
------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/19 20:27
Start Date: 19/Mar/19 20:27
Worklog Time Spent: 10m
Work Description: yukuai518 commented on issue #2573: [GOBBLIN-703] Allow
planning job to be running in non-blocking mode
URL:
https://github.com/apache/incubator-gobblin/pull/2573#issuecomment-474568538
@htran1 could you help review?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 215714)
Time Spent: 20m (was: 10m)
> 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
> Time Spent: 20m
> 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)
