Skip to content

Surface LogStreamAccumulator temp-file removal failures as warnings#66663

Merged
potiuk merged 1 commit into
apache:mainfrom
dheerajturaga:fix-log-stream-accumulator-warning-level
May 10, 2026
Merged

Surface LogStreamAccumulator temp-file removal failures as warnings#66663
potiuk merged 1 commit into
apache:mainfrom
dheerajturaga:fix-log-stream-accumulator-warning-level

Conversation

@dheerajturaga
Copy link
Copy Markdown
Member

Failure to remove the spill file is the exact failure mode that caused the prior /tmp leak (~39 GB on a single host), so operators need it visible in their logs rather than buried at debug level.

Follow-up to #66450.

Failure to remove the spill file is the exact failure mode that
caused the prior /tmp leak (~39 GB on a single host), so operators
need it visible in their logs rather than buried at debug level.

Follow-up to apache#66450.
@potiuk potiuk added the backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch label May 10, 2026
@potiuk potiuk added this to the Airflow 3.2.2 milestone May 10, 2026
@potiuk potiuk merged commit 1abd959 into apache:main May 10, 2026
71 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test PR Link

github-actions Bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request May 10, 2026
…s warnings (apache#66663)

Failure to remove the spill file is the exact failure mode that
caused the prior /tmp leak (~39 GB on a single host), so operators
need it visible in their logs rather than buried at debug level.

Follow-up to apache#66450.
(cherry picked from commit 1abd959)

Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
potiuk pushed a commit that referenced this pull request May 10, 2026
…s warnings (#66663) (#66669)

Failure to remove the spill file is the exact failure mode that
caused the prior /tmp leak (~39 GB on a single host), so operators
need it visible in their logs rather than buried at debug level.

Follow-up to #66450.
(cherry picked from commit 1abd959)

Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
vatsrahul1001 pushed a commit that referenced this pull request May 20, 2026
…s warnings (#66663) (#66669)

Failure to remove the spill file is the exact failure mode that
caused the prior /tmp leak (~39 GB on a single host), so operators
need it visible in their logs rather than buried at debug level.

Follow-up to #66450.
(cherry picked from commit 1abd959)

Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:logging backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants