Gcsfuse v2.7.0

Write Stability improvements: Reduces write tail latencies by increasing the number of retries in case of a write operation stall. The retries are configured to kick in if the stall is greater than 10 seconds. This feature will enhance the application's ability to successfully complete write operations, especially for large files such as checkpoint writes.

Bug Fixes & Improvements:

1. gRPC: Fixed a rare pre-condition error in gRPC client protocol. The pre-condition error arises when moving a directory to an empty directory. PR#2838
2. Negative metadata caches entries upon the deletion of an object/folder. PR#2822

Dependency Upgrades / CVE fixes:

1. Fixing CVE in the crypto library. PR #2809
2. Upgraded dependencies for better stability
   i. go-lang version from 1.23.3 to 1.23.4
   ii. Other dependency upgrade
   PR#2762 , PR#2756, PR#2757, PR#2758, PR#2759, PR#2760, PR#2761, PR#2731

Gcsfuse v2.5.2

Dependency Upgrades / CVE fixes:
This release is built on top of v2.5.1 with the additional security/CVE fixes for indirect dependency x/crypto library.

Gcsfuse v2.6.0

gRPC:

• A new gRPC client version provides significant read performance improvements at lower CPU utilization.
• Allowlist access is no longer needed to use gRPC. To use gRPC, pass the cli flag --client-protocol=grpc OR add gcs-connection:client-protocol: grpc in the mount-config file.
• Known issues:
  • gRPC: File system write operation hangs while repeatedly writing over a single > 16MiB file - Issue#2784
  • gRPC: File system returns Input/output error while repeatedly writing over a single < 16MiB file - Issue#2783

List Payload Reduction:

• The Cloud Storage ListObjects API now retrieves only essential GCS object attributes required for serving list requests, resulting in significantly less response payloads and reduced latency. PR#2627

Bug Fixes & Improvements:

• All flags are now supported in the persistent mounting via /etc/fstab. PR#2478
• SIGTERM to unmount: Sending SIGTERM signal to GCSFuse process will now unmount the filesystem.
• Enhanced error handling for background processes now captures runtime crash logs. Users can specify a log file path to store these logs (the file will have a .stderr extension).

Gcsfuse v2.5.1

Bug Fixes:
Improved error handling: GCSFuse will now retry requests to hierarchical namespace bucket APIs that encounter deadline exceeded errors. This improves stability and prevents unnecessary failures, especially in high latency environments.

Gcsfuse v2.5.0

• Hierarchical Namespace Enabled Buckets: With this release users can also mount buckets with hierarchical namespace enabled. HNS-enabled buckets offer several advantages over standard buckets when used with cloud storage fuse:
  • Renaming directories is now supported natively with Hierarchical Namespace Buckets, where Rename operation is fast and atomic to benefit workloads such as AI/ML checkpointing.
  • Users don't need to specify the --implicit-dirs command-line option when using hierarchical namespace enabled buckets. HNS buckets inherently understand directories, so gcsfuse does not need to simulate directories using placeholder objects ( 0-byte objects ending with '/' ).
  • Kernel’s Lookup operations are also improved in HNS buckets. The Objects.list api is replaced with a more efficient Folder:get api.
• Config CLI Parity:
  • All params in config-file will be available as CLI flags and vice versa going forward. Documentation links:
    • CLI Flags
    • Config File
  • Deprecated and hidden flags won't show up in the help-doc any more.
• Write Enhancements:
  • Information of newly created files is added to the type cache. This helps reduce an additional GCS list call if the bucket has been mounted with –implicit-dirs flag. (PR#2303)
• Deprecated - The flags --debug_gcs and --debug_fuse flags are now deprecated. Set --log-severity=TRACE to achieve the same behavior.

Gcsfuse v2.4.1

• Bug Fixes & Improvements:
  • Fix for os.RemoveAll(directory) failure with kernel list cache and remote file addition: PR#2163.
  • Fixed an issue in listing during creation of files in the same directory (Issue#2220, PR#2237).
  • Additional performance improvements when using Parallel downloads (PR#2287).
• Metrics:
  • Categorize the various (approximately 150) fs_errors into a handful of categories. This helps reduce the upper bound of cardinality of these error labels which avoids it from getting dropped by the Google Cloud Metrics pipeline (PR#2321, PR#2382, PR#2390).
  • Change unit of ops and file-cache latency metrics to microseconds to improve the resolution of these metrics (PR#2380).
• Dependency Upgrades / CVE fixes:
  • Upgraded dependencies for better stability (PR#2301, PR#2355, PR#2364)
  • Upgrade Golang version to 1.23.0 (PR#2365)

Gcsfuse v2.1.1

This release is built on top of v2.1.0 with the additional security fixes of Golang upgrade to 1.22.4

Gcsfuse v2.4.0

• Parallel download:
  • Accelerates reads of large files, by using the file cache directory as a prefetch buffer using multiple workers to download large files in parallel.
  • This feature is useful for single threaded read scenarios that load large (>1GiB) files, such as model serving use cases and checkpoint restores.
  • This feature is disabled by default. To enable this feature:
    • Enabling the file cache feature (GKE instructions) is a prerequisite for using the parallel download feature, which uses the cache directory as a prefetch buffer. Although a cache is typically associated with repeat reads, with parallel downloads even first reads of large files are accelerated.
      • The file being read must fit within the file cache directory’s available capacity, which can be controlled by max-size-mb. A value of “-1” allows it to use the cache volume’s entire capacity, or you can give it a value in Megabytes.
      • If the same file will be read multiple times, increase the ttl-secs value. A value of "-1" bypasses TTL expiration and serves the file from the cache if it's available.
    • Set file-cache:enable-parallel-downloads:true in the config file to enable parallel downloads. The default is false.
    • Additional optional parameters:
      • file-cache:parallel-downloads-per-file: The number of maximum workers to spawn per file to download the object from GCS into the file-cache. Default is 16.
      • file-cache:max-parallel-downloads: The number of maximum workers that can be spawned at any given time across all the download jobs of files. The default is set to 2x the number of CPU cores on the machine. A value of -1 means no limit.
      • file-cache:download-chunk-size-mb: The size of each read request in MiB that each goroutine makes to GCS when downloading the object into file-cache. Default is 50. A parallel download will only trigger if the file being read is => this value specified
    • Note: If your application does high read parallelism (>8 threads), a slight performance degradation may be observed if using this feature. High read parallelism is typically seen in training workloads so should not be used for training workloads, and is therefore recommended only for model serving and checkpoint restores, which are typically single threaded large file reads.
  • Addresses #1300
• Kernel-List-Cache
  • List responses, that happen as a part of a readdir operation, are cached in the kernel page cache. This can significantly speed up AI/ML training runs, which do full directory listing first, by serving repeat ListObjects calls locally from the kernel page cache. Due to potential coherency/consistency issues, it is recommended to use on read only volumes, specifically for serving and training.
  • This feature is disabled by default. To enable this feature:
    • Control cache invalidation via the --kernel-list-cache-ttl-secs cli flag or file-system:kernel-list-cache-ttl-secs config flag, where a value of:
      • 0 means disabled. This is the default value.
      • valid positive - represents the ttl (in seconds) to keep the directory list response in the kernel page-cache.
      • -1 to bypass a TTL expiration and serve the list response from the cache whenever it's available.
  • Addresses #184
• CLI-flags Take Precedence over Config, behavior change for logging-flags: Going forward command-line flags will always take precedence for all settings. Change in behavior for logging flags (--log-file & --log-format), where config was taking precedence but not cli-flags will take. This will affect only if the same settings are set in both CLI and config. - #2077

Dependency Upgrades / CVE fixes:

• Upgraded dependencies for better stability (PR #2209, #2196, #2195, #2086)

Gcsfuse v2.3.2

This release includes:

• Code changes/fixes to kernel list cache feature.

Full Changelog: v2.3.1...v2.3.2

Gcsfuse v2.3.1

Enhancements:

• Hotfix release to restore backward compatibility for the experimental KernelListCacheTtlSecs that got broken in version v2.3.0
  • Cache invalidation can be controlled via the --kernel-list-cache-ttl-secs cli flag or file-system:kernel-list-cache-ttl-secs config flag

Dependency Upgrades / CVE fixes:

• No Changes here.

What's Changed

• Revert "Move KernelListCacheTtlSecs to List by @kislaykishore in #2083

Full Changelog: v2.3.0...v2.3.1