[
https://issues.apache.org/jira/browse/GOBBLIN-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Krishna updated GOBBLIN-1674:
-------------------------------------
Description:
The gobbiln.sh script is using "start" command to start the script, and since
the job command uses "nohup" and "&" , the job runs in the background.
We have some use-case where we need to know whether the script completed
successfully so that we can crawl some logs and export some metrics.
But now, that part is breaking and not able to figure out if script finished.
(This is a breaking change from [Gobblin
0.14|https://github.com/apache/gobblin/blob/ad32bba684f4c004801b6983bc52c126df2f04b2/bin/gobblin-mapreduce.sh#L206]
to [Gobblin
0.16|https://github.com/apache/gobblin/blob/b400089035fe7ada1a523f9b7e5321e11d46d651/bin/gobblin.sh#L485]
in this aspect).
So it will be useful to add an optional argument to specify whether to run in
background or not, especially when scheduling Gobblin jobs through crontab,
running in background doesn't seem relevant.
was:
The gobbiln.sh script is using "start" command to start the script, and since
the job command uses "nohup" and "&" , the job runs in the background.
We have some use-case where we need to know whether the script completed
successfully so that we can crawl some logs and export some metrics.
But now, that part is breaking and not able to figure out if script finished.
(This is a breaking change from Gobblin 14 to 16 in this aspect).
So it will be useful to add an optional argument to specify whether to run in
background or not, especially when scheduling Gobblin jobs through crontab,
running in background doesn't seem relevant.
> gobblin.sh script to make running in background optional
> --------------------------------------------------------
>
> Key: GOBBLIN-1674
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1674
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-service
> Reporter: Bharath Krishna
> Priority: Major
>
> The gobbiln.sh script is using "start" command to start the script, and since
> the job command uses "nohup" and "&" , the job runs in the background.
> We have some use-case where we need to know whether the script completed
> successfully so that we can crawl some logs and export some metrics.
> But now, that part is breaking and not able to figure out if script finished.
> (This is a breaking change from [Gobblin
> 0.14|https://github.com/apache/gobblin/blob/ad32bba684f4c004801b6983bc52c126df2f04b2/bin/gobblin-mapreduce.sh#L206]
> to [Gobblin
> 0.16|https://github.com/apache/gobblin/blob/b400089035fe7ada1a523f9b7e5321e11d46d651/bin/gobblin.sh#L485]
> in this aspect).
> So it will be useful to add an optional argument to specify whether to run in
> background or not, especially when scheduling Gobblin jobs through crontab,
> running in background doesn't seem relevant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
