[
https://issues.apache.org/jira/browse/GOBBLIN-2033?focusedWorklogId=913521&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-913521
]
ASF GitHub Bot logged work on GOBBLIN-2033:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/24 20:40
Start Date: 08/Apr/24 20:40
Worklog Time Spent: 10m
Work Description: ZihanLi58 commented on PR #3910:
URL: https://github.com/apache/gobblin/pull/3910#issuecomment-2043607154
Two questions here:
1. Why do we try to use taskAttempId instead of one random UUID? It's still
possible that same task get retried in the same container?
2. Why do we want to avoid removing orphan files from the previous run? Any
concern related to that?
Issue Time Tracking
-------------------
Worklog Id: (was: 913521)
Time Spent: 0.5h (was: 20m)
> Append HelixInstanceName to task runner staging paths
> -----------------------------------------------------
>
> Key: GOBBLIN-2033
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2033
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Matthew Ho
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> During the shutdown of a task runner, it's possible to write bad files to the
> staging area. On startup of a new task runner, it should not try to reuse
> that old file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
