[PR #545] [MERGED] Changed base cached time of stat_cache_expire option - #523 #1539

Closed
opened 2026-03-04 02:00:56 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/545
Author: @ggtakec
Created: 3/19/2017
Status: Merged
Merged: 3/19/2017
Merged by: @ggtakec

Base: masterHead: master


📝 Commits (1)

  • 523043a Changed base cached time of stat_cache_expire option - #523

📊 Changes

4 files changed (+28 additions, -11 deletions)

View changed files

📝 doc/man/s3fs.1 (+5 -1)
📝 src/cache.cpp (+14 -9)
📝 src/cache.h (+2 -1)
📝 src/s3fs.cpp (+7 -0)

📄 Description

Relevant Issue (if applicable)

#523

Details

s3fs updated the cached time of stat information to the time when it was accessed to that cache.
This effectively reduces the number of requests for continuous cache access.
However, if the bucket is mounted with multiple s3fs, it becomes a problem like #523.

In this renovation, the expiration date specified by "stat_cache_expire" shall be the time since stat information was cached.
And I added an option called "stat_cache_interval_expire" to update the cached time when accessed stat information for compatibility.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/545 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 3/19/2017 **Status:** ✅ Merged **Merged:** 3/19/2017 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`523043a`](https://github.com/s3fs-fuse/s3fs-fuse/commit/523043a2aa03ce7521c77ea494a22b16323b768e) Changed base cached time of stat_cache_expire option - #523 ### 📊 Changes **4 files changed** (+28 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `doc/man/s3fs.1` (+5 -1) 📝 `src/cache.cpp` (+14 -9) 📝 `src/cache.h` (+2 -1) 📝 `src/s3fs.cpp` (+7 -0) </details> ### 📄 Description #### Relevant Issue (if applicable) #523 #### Details s3fs updated the cached time of stat information to the time when it was accessed to that cache. This effectively reduces the number of requests for continuous cache access. However, if the bucket is mounted with multiple s3fs, it becomes a problem like #523. In this renovation, the expiration date specified by "stat_cache_expire" shall be the time since stat information was cached. And I added an option called "**stat_cache_interval_expire**" to update the cached time when accessed stat information for compatibility. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-04 02:00:56 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#1539
No description provided.