[
https://issues.apache.org/jira/browse/GOBBLIN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apekshit Kumar updated GOBBLIN-1963:
------------------------------------
Description:
*Context:*
Following a restart, Gobblin service is currently unable to process previous
jobs in the RUNNING/LAUNCHED/SUBMITTED state, resulting in a stuck state for
these jobs.
A job is in the LAUNCHED state, and while calculating CDC, the Application
master got re-attempted, actually due to name node issue (can be any env
issues).
*Acceptance Criteria:*
# The system should automatically resume jobs that were in the
RUNNING/LAUNCHED/SUBMITTED state after the restart.
# The solution should address lingering locks acquired in the previous run.
# Care should be taken to avoid picking up jobs or cleaning locks that are
currently being handled by other deployments as part of work stealing.
#
was:
*Context:*
Following a restart, Gobblin service is currently unable to process previous
jobs in the RUNNING/LAUNCHED/SUBMITTED state, resulting in a stuck state for
these jobs.
*Acceptance Criteria:*
# The system should automatically resume jobs that were in the
RUNNING/LAUNCHED/SUBMITTED state after the restart.
# The solution should address lingering locks acquired in the previous run.
# Care should be taken to avoid picking up jobs or cleaning locks that are
currently being handled by other deployments as part of work stealing.
> Following the restart, jobs that were previously in the "RUNNING,"
> "LAUNCHED," or "SUBMITTED" state failed to resume.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1963
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1963
> Project: Apache Gobblin
> Issue Type: Bug
> Components: misc
> Affects Versions: 0.15.0
> Reporter: Apekshit Kumar
> Priority: Minor
>
> *Context:*
> Following a restart, Gobblin service is currently unable to process previous
> jobs in the RUNNING/LAUNCHED/SUBMITTED state, resulting in a stuck state for
> these jobs.
>
> A job is in the LAUNCHED state, and while calculating CDC, the Application
> master got re-attempted, actually due to name node issue (can be any env
> issues).
> *Acceptance Criteria:*
> # The system should automatically resume jobs that were in the
> RUNNING/LAUNCHED/SUBMITTED state after the restart.
> # The solution should address lingering locks acquired in the previous run.
> # Care should be taken to avoid picking up jobs or cleaning locks that are
> currently being handled by other deployments as part of work stealing.
> #
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
