这是indexloc提供的服务,不要输入任何密码
Skip to content

Gcsfuse v3.1.0

Latest
Compare
Choose a tag to compare
@gcsfuse-github-machine-user-bot gcsfuse-github-machine-user-bot released this 08 Jul 09:33
· 79 commits to master since this release

Renaming Objects with MoveObject API:

Starting with this release, we're transitioning from the "copy-and-delete" method to the more robust MoveObject API. This change brings atomic rename compatibility, meaning that all renaming operations will now be completed as a single, indivisible process.

Enhanced Read Reliability and Reduced Read Tail Latency

Starting in v3.1.0, GCSFuse improves read reliability and helps reduce read tail latencies by automatically detecting and retrying stalled GET requests. This feature uses a dynamic timeout based on historical successful or canceled request latency to identify and retry the slowest 1% of reads, which are the primary contributors to tail latency. If a request times out, it is retried using an exponential backoff algorithm.

Automatic Inactive Read Streams Closure:

This improves GCS server-side resource (tcp connections, memory) utilization by automatically closing inactive GCSFuse read streams after a reasonable timeout (between 10s to 20s). Especially important for large scale AI/ML training workloads. Inactive read streams often result from workloads that keep file handles open and idle for some time after reading only a portion of data. If the workload performs the read after the stream closure, it is still expected to read, however with an additional delay of establishing the stream again.

Bug fixes & Improvements:

  • An improvement where GCSFuse would unnecessarily consume CPU cycles due to improper Jacobsa/Fuse logger initialization. Loggers now initialize as configured (e.g., OFF, INFO). - PR

Dependency Upgrades / CVE fixes

  • Fix vulnerability go-viper/mapstructure - PR