[
https://issues.apache.org/jira/browse/GOBBLIN-1634?focusedWorklogId=763320&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763320
]
ASF GitHub Bot logged work on GOBBLIN-1634:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/22 07:04
Start Date: 28/Apr/22 07:04
Worklog Time Spent: 10m
Work Description: Will-Lo commented on PR #3495:
URL: https://github.com/apache/gobblin/pull/3495#issuecomment-1111824304
Ah I got my events mixed up, the SKIPPED_TIME is actually emitted by Helix
in GobblinCluster so it's never actually sent from GaaS' internal system, and
shouldn't be retried. I think the switch statement not having the comment is
fine if we go with the semantic naming like you suggested.
Issue Time Tracking
-------------------
Worklog Id: (was: 763320)
Time Spent: 1h 10m (was: 1h)
> 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
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
