Native s3 Filesystem Blog#860
Open
Samrat002 wants to merge 1 commit into
Open
Conversation
| slug: "announcing-native-s3-fs" | ||
| url: "/2026/06/14/announcing-native-s3-fs/" | ||
| authors: | ||
| - gabor: |
Contributor
There was a problem hiding this comment.
Are there github names?
Contributor
|
cc @davidradl if you have some time, since you're native 🙂 |
davidradl
reviewed
Jun 15, 2026
|
|
||
| Apache Flink relies on the underlying filesystem for much of its work: reading and writing application data, materializing streaming sinks, and storing checkpoints and savepoints for recovery. For years, S3 support in Flink meant choosing between two Hadoop-based plugins, each with its own trade-offs and configuration quirks. With Flink 2.3, there is a better option. | ||
|
|
||
| Today we're introducing `flink-s3-fs-native`, A ground-up, Hadoop-free S3 filesystem built specifically for Flink. It ships as an experimental opt-in plugin in Flink 2.3, is already running in production at scale at major technology companies, and delivers measurable, reproducible performance gains. |
Contributor
There was a problem hiding this comment.
I wonder if the op-in plugin could be turned into a hyperlink to a section that describes it.
davidradl
reviewed
Jun 15, 2026
|
|
||
| | | | | ||
| |---|---| | ||
| | **~2x faster checkpoints** | 48.8 s average vs 90.1 s with the Presto plugin; up to 4.5x at small state sizes | |
Contributor
There was a problem hiding this comment.
maybe point to the test section with a hyper link
davidradl
reviewed
Jun 15, 2026
| | **~2x faster checkpoints** | 48.8 s average vs 90.1 s with the Presto plugin; up to 4.5x at small state sizes | | ||
| | **Drop-in replacement** | Swap the JAR, keep your existing `flink-conf.yaml`, restart your cluster | | ||
| | **No Hadoop dependency** | ~13 MB JAR vs ~30–93 MB; no CVE triage on Hadoop transitive dependencies | | ||
| | **AWS SDK v2** | Async-first I/O; AWS SDK v1 entered maintenance mode December 2025 | |
Contributor
There was a problem hiding this comment.
hyper links for the AWS things and end date would be helpful.
davidradl
reviewed
Jun 15, 2026
|
|
||
| Both share a common base layer that adapts a Hadoop `FileSystem` into a Flink `FileSystem`. This adaptation layer adds indirection, limits Flink-specific optimizations, and ties the implementation to Hadoop's configuration model and SDK lifecycle. | ||
|
|
||
| As a result, you could have exactly-once sinks or a lighter read path, but not both. In addition, you are carrying Hadoop dependency hell. |
davidradl
reviewed
Jun 15, 2026
|
|
||
| ### Test environment | ||
|
|
||
| The benchmark ran on Amazon EKS (ap-south-1) with a Flink 2.1.1 cluster composed of 1 JobManager (2 GB memory, 1 core) and 2 TaskManagers (6 GB memory, 1.5 cores, 4 task slots each) for a total parallelism of 8. The workload targeted 20 GB of RocksDB state with full, non-incremental checkpoints every 60 seconds in EXACTLY_ONCE mode. The test ran for approximately 77 minutes. Configurations for both plugins were identical except for the plugin JAR itself. |
Contributor
There was a problem hiding this comment.
Add a caveat that users performance might differ.
Can we point to the payloads - so users can run exactly this benchmark?
davidradl
reviewed
Jun 15, 2026
| - **Enhanced observability** : S3 operation metrics (latency, retry counts, throughput) exposed through Flink's metric system, giving platform teams visibility into S3 I/O behavior. | ||
| - **Stream-based S3 read/write** : Improving memory efficiency for large object operations. | ||
|
|
||
| **Phase 2: Recommended default.** Once stability is proven across a broad set of community deployments, the native plugin will be promoted to the recommended default for new Flink installations. Documentation, quickstarts, and tutorials will be updated accordingly. |
Contributor
There was a problem hiding this comment.
how will be know that "proven across a broad set of community deployments" has happened.
davidradl
reviewed
Jun 15, 2026
|
|
||
| **Phase 2: Recommended default.** Once stability is proven across a broad set of community deployments, the native plugin will be promoted to the recommended default for new Flink installations. Documentation, quickstarts, and tutorials will be updated accordingly. | ||
|
|
||
| **Phase 3: Legacy deprecation.** The Hadoop and Presto plugins will be formally deprecated with a defined support window before removal. |
Contributor
There was a problem hiding this comment.
we could deprecate in phase 1. As we do not intend to enhance these connectors.
davidradl
reviewed
Jun 15, 2026
|
|
||
| `flink-s3-fs-native` is part of Apache Flink and is developed in the open. The module lives at `flink-filesystems/flink-s3-fs-native` in the [Flink repository](https://github.com/apache/flink). | ||
|
|
||
| The migration is safe and requires minimal deployment changes. If your team is already evaluating or running this in production, we want to hear from you. Your feedback directly shapes the path from experimental to default. |
Contributor
There was a problem hiding this comment.
Maybe be explicit as to how to contact us about this. Is there a tag that should be used in a dev list post?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.