Skip to content

Conversation

RocMarshal
Copy link
Contributor

What is the purpose of the change

  • BP for FLINK-38344
  • Fix the bug that The local files of the HistoryServer may risk never being deleted.

Brief change log

In the HistoryServer constructor, first clear all files in the historyserver.web.tmpdirdirectory before proceeding with the original initialization logic. This ensures that the local files marked for cleanup—based on HistoryServerArchiveFetcher#cachedArchivesPerRefreshDirectory—are free from leaks.

Verifying this change

This change is already covered by existing tests.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
  • The serializers: (yes / no / don't know)
  • The runtime per-record code paths (performance sensitive): (yes / no / don't know)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
  • The S3 file system connector: (yes / no / don't know)

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

…storyServer may risk never being deleted.

(cherry picked from commit 39a4628)
@flinkbot
Copy link
Collaborator

flinkbot commented Sep 26, 2025

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants