Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Repeated initialization of FileSystems is problematic #27535

Closed
1 of 15 tasks
mosche opened this issue Jul 18, 2023 · 0 comments · Fixed by #26694
Closed
1 of 15 tasks

[Bug]: Repeated initialization of FileSystems is problematic #27535

mosche opened this issue Jul 18, 2023 · 0 comments · Fixed by #26694

Comments

@mosche
Copy link
Member

mosche commented Jul 18, 2023

What happened?

Current initialization of FileSystems through FileSystems.setDefaultPipelineOptions is problematic and prone to race conditions, especially when triggered on deserialization of SerializablePipelineOptions (see #18430, BEAM-14465, BEAM-14355).

Particularly with S3FileSystem this is bad as it can easily leak resources (threads!) if used this way (see #26321).

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant