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

Posted to dev@gobblin.apache.org by "Sudarshan Vasudevan (JIRA)" <ji...@apache.org> on 2018/03/01 05:11:00 UTC

[jira] [Updated] (GOBBLIN-418) Change Gobblin Service behavior to not call addSpec for pre-existing specs on start up

     [ https://issues.apache.org/jira/browse/GOBBLIN-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudarshan Vasudevan updated GOBBLIN-418:
----------------------------------------
    Summary: Change Gobblin Service behavior to not call addSpec for pre-existing specs on start up    (was: Change Gobblin Service behavior to not call addSpec for pre-existing specs on listener registration   )

> Change Gobblin Service behavior to not call addSpec for pre-existing specs on start up  
> ----------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-418
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-418
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-service
>    Affects Versions: 0.13.0
>            Reporter: Sudarshan Vasudevan
>            Assignee: Abhishek Tiwari
>            Priority: Minor
>             Fix For: 0.13.0
>
>
> When Gobblin Service flowCatalog registers job scheduler, it calls addSpec() for each of the pre-existing Specs. This has the unwanted side-effect of every Spec being forwarded to the leader and being executed in case flowRunImmediately is enabled.



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