juicedata /juicefs
JuiceFS is a distributed POSIX file system built on top of Redis and S3.
★ 14,738⑂ 1,358👁 120⑃ 5,102● 2,065▤ 61
+2
Daily
+112
Weekly
+210
Monthly
14,738
stars
1,358
forks
120
watchers
5,102
prs
2,065
issues
61
releases
README
JuiceFS is a high-performance POSIX file system released under Apache License 2.0, particularly designed for the cloud-native environment. The data, stored via JuiceFS, will be persisted in Object Storage _(e.g. Amazon S3)_, and the corresponding metadata can be persisted in various compatible database engines such as Redis, MySQL, and TiKV based on the scenarios and requirements. With JuiceFS, massive cloud storage can be directly connected to big data, machine learning, artificial intelligence, and various application platforms in production environments. Without modifying code, the massive cloud storage can be used as efficiently as local storage. 📖 Document: Quick Start Guide Highlighted Features 1. Fully POSIX-compatible: Use as a local file system, seamlessly docking with existing applications without breaking business workflow. 2. Fully Hadoop-compatible: JuiceFS' Hadoop Java SDK is compatible with Hadoop 2.x and Hadoop 3.x as well as a variety of components in the Hadoop ecosystems. 3. S3-compatible: JuiceFS' S3 Gateway provides an S3-compatible interface. 4. Cloud Native: A Kubernetes CSI Driver is provided for easily using JuiceFS in Kubernetes. 5. Shareable: JuiceFS is a shared file storage that can be read and written by thousands of clients. 6. Strong Consistency: The confirmed modification will be immediately visible on all the servers mounted with the same file system. 7. Outstanding Performance: The latency can be as low as a few milliseconds, and the throughput can be expanded nearly unlimitedly _(depending on the size of the Object Storage)_. Test results 8. Data Encryption: Supports data encryption in transit and at rest (please refer to the guide for more information). 9. Global File Locks: JuiceFS supports both BSD locks (flock) and POSIX record locks (fcntl). 10. Data Compression: JuiceFS supports LZ4 or Zstandard to compress all your data. --- Architecture | Getting Started | Advanced Topics | POSIX Compatibility | Performance Benchmark | Supported Object Storage | Who is using | Roadmap | Reporting Issues | Contributing | Community | Usage Tracking | License | Credits | FAQ --- Architecture JuiceFS consists of three parts: 1. JuiceFS Client: Coordinates Object Storage and metadata storage engine as well as implementation of file system interfaces such as POSIX, Hadoop, Kubernetes, and S3 gateway. 2. Data Storage: Stores data, with supports of a variety of data storage media, e.g., local disk, public or private cloud Object Storage, and HDFS. 3. Metadata Engine: Stores the corresponding metadata that contains information of file name, file size, permission group, creation and modification time and directory structure, etc., with supports of different metadata engines, e.g., Redis, MySQL, SQLite and TiKV. !JuiceFS Architecture JuiceFS can store the metadata of file system on different metadata engines, like Redis, which is a fast, open-source, in-memory key-value data storage, particularly suitable for storing
Top issues
#2877CPU usage keep increasing when memcached enabled using Elasticache13 comments · 2022-10-19#3143Writeback cache synchronization issue11 comments · 2022-12-31#345Allow utilizing multiple buckets as backend storage endpoints11 comments · 2021-04-23#3030Using for timemachine backup 10 comments · 2022-11-28#7462Watchdog kill timing is slower than session stale-cleanup, allowing a frozen client to resume and write after its locks were revoked9 comments · 2026-08-26#5254Better alternatives for data encryption9 comments · 2024-10-25#4209use source code to compile juicefs-hadoop-client.jar is only 33.44MB, too less than the public jar, use self compile jar can't start hadoop8 comments · 2023-11-28#2943automation: advanced ansible support8 comments · 2022-11-02
Discussions
#7713JuiceFS v1.4.1: Is ~23× object I/O amplification expected for small random reads and overwrites?1 comments · 2026-10-19#7700Overwritten data retained after writes stop in v1.4.1 — expected behavior and a proposed fix1 comments · 2026-10-15#7690Is NewVFS intended to be constructed only once per process?1 comments · 2026-10-14#7590Any timeline/plan for the next release v1.4.2?1 comments · 2026-09-29#7483Contributor experience1 comments · 2026-08-31#7461A revoked (stale-session) lock holder can still write — locks are revoked without fencing2 comments · 2026-08-26#7427Possible missed FlushTo dispatch when slice ID is allocated asynchronously1 comments · 2026-08-20#7359Snapshots - Matadata backups1 comments · 2026-08-05
Latest release
v1.4.2 v1.4.2 2026-10-22This is the second patch release for JuiceFS v1.4. It has 33 commits from 13 contributors, thanks to @jiefenghuang @zhijian-pro @solracsf @zxh326 @myangitzh @polyrabbit @gmaruzz @kungf @nueks @prOOrc @stevapple @YuarenArt @zhitaoli-6 Bugfix - chunk: prevent incorrect reads after object storage timeouts (7503, 7500, 7509, 7520) - chunk: prevent zstd decompression from overwriting adjacent slices (7556) - vfs/meta: fix ioctl flag permission checks and prevent clearing unrelated flags (7408, 7694) - fuse: prevent unintended tier resets with writeback caching (7697) - meta: fix format r