[
https://issues.apache.org/jira/browse/GOBBLIN-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Lo updated GOBBLIN-1634:
--------------------------------
Description:
On Gobblin as a Service flows can fail SLAs if they do not receive a Kafka
event in some designated amount of time.
Since GaaS supports retrys on failures, these failures due to SLAs should also
be retryable.
However, if the flow is cancelled from a user specified event through the API
we do not want to retry.
Additionally, we also do not want to retry if a flow is skipped due to
concurrent jobs running at the same time, as it is unlikely without a more
sophisticated waiting algorithm that the job will be finished by the time the
job is retried again, wasting resources.
was:
On Gobblin as a Service flows can fail SLAs if they do not receive a Kafka
event in some designated amount of time.
Since GaaS supports retrys on failures, these failures due to SLAs should also
be retryable.
> GaaS Flow SLA Kills should be retryable if configured
> -----------------------------------------------------
>
> Key: GOBBLIN-1634
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1634
> Project: Apache Gobblin
> Issue Type: Task
> Reporter: William Lo
> Priority: Major
>
> On Gobblin as a Service flows can fail SLAs if they do not receive a Kafka
> event in some designated amount of time.
> Since GaaS supports retrys on failures, these failures due to SLAs should
> also be retryable.
> However, if the flow is cancelled from a user specified event through the API
> we do not want to retry.
> Additionally, we also do not want to retry if a flow is skipped due to
> concurrent jobs running at the same time, as it is unlikely without a more
> sophisticated waiting algorithm that the job will be finished by the time the
> job is retried again, wasting resources.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
