[jira] [Updated] (BEAM-1507) java DataflowRunner should warn if the stagingLocation has a TTL

["Kenneth Knowles (Jira)" <ji...@apache.org>]

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

Kenneth Knowles updated BEAM-1507:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> java DataflowRunner should warn if the stagingLocation has a TTL
> ----------------------------------------------------------------
>
>                 Key: BEAM-1507
>                 URL: https://issues.apache.org/jira/browse/BEAM-1507
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Dan Halperin
>            Priority: P3
>              Labels: newbie, starter
>
> We have seen a few customers run into a hard-to-track-down bug where the staging bucket has a TTL, but files get TTL-deleted when they are still needed.
> This might be because of:
> 1. Long lived batch jobs / streaming jobs can reference staged files arbitrarily later and will fail in bad ways if they have been deleted.
> 2. Some customers even hit issues where the "check file already exists" succeeds when starting a job, but then the file is TTL-deleted before the job actually starts. (This sounds crazy, but may happen if TTL is 7 days and jobs run every 7 days, for example. Race condition.)
> I'm hoping it's not hard to check that files would have TTLs and warn if so.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)