apache/beam

py DataflowRunner should warn if the stagingLocation has a TTL

Open

#18,123 opened on Jun 3, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,097 forks)batch import
P3coregood first issueimprovementpython

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 6d) (243 merged PRs in 30d)

Description

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.

Imported from Jira BEAM-1506. Original Jira may contain additional context. Reported by: dhalperi.

Contributor guide

Research direction
Examine how to fetch bucket lifecycle rules via Google Cloud Storage client and add a warning to the DataflowRunner if a TTL is set.
Tech stack
python
Domain
backendcloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGoogle Cloud Storage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60