JuiceFS is a high-performance POSIX file system released under GNU Affero General Public License v3.0. It is specially optimized for the cloud-native environment. Using the JuiceFS to store data, the data itself will be persisted in object storage (e.g. Amazon S3), and the metadata corresponding to the data can be persisted in various database engines such as Redis, MySQL, and SQLite according to the needs of the scene.
JuiceFS can simply and conveniently connect massive cloud storage directly to big data, machine learning, artificial intelligence, and various application platforms that have been put into production environment, without modifying the code, you can use massive cloud storage as efficiently as using local storage.
- Fully POSIX-compatible: Use like a local file system, seamlessly docking with existing applications, no business intrusion.
- Fully Hadoop-compatible: JuiceFS Hadoop Java SDK is compatible with Hadoop 2.x and Hadoop 3.x. As well as variety of components in Hadoop ecosystem.
- S3-compatible: JuiceFS S3 Gateway provides S3-compatible interface.
- Cloud Native: JuiceFS provides Kubernetes CSI driver to help people who want to use JuiceFS in Kubernetes.
- Sharing: JuiceFS is a shared file storage that can be read and written by thousands clients.
- Strong Consistency: The confirmed modification will be immediately visible on all servers mounted with the same file system .
- Outstanding Performance: The latency can be as low as a few milliseconds and the throughput can be expanded to nearly unlimited. Test results
- Data Encryption: Supports data encryption in transit and at rest, read the guide for more information.
- Global File Locks: JuiceFS supports both BSD locks (flock) and POSIX record locks (fcntl).
- Data Compression: JuiceFS supports use LZ4 or Zstandard to compress all your data.
Architecture | Getting Started | Administration | POSIX Compatibility | Performance Benchmark | Supported Object Storage | Status | Roadmap | Reporting Issues | Contributing | Community | Usage Tracking | License | Credits | FAQ
JuiceFS consists of three parts:
- JuiceFS Client: Coordinate the implementation of object storage and metadata storage engines, as well as file system interfaces such as POSIX, Hadoop, Kubernetes, and S3 gateway.
- Data Storage: Store the data itself, support local disk and object storage.
- Metadata Engine: Metadata corresponding to the stored data, supporting multiple engines such as Redis, MySQL, and SQLite;
JuiceFS relies on Redis to store file system metadata. Redis is a fast, open-source, in-memory key-value data store and very suitable for storing the metadata. All the data will store into object storage through JuiceFS client. Learn more
Any file stored in JuiceFS will be split into fixed-size "Chunk", and the default upper limit is 64 MiB. Each Chunk is composed of one or more "Slice". The length of the slice is not fixed, depending on the way the file is written. Each slice will be further split into fixed-size "Block", which is 4 MiB by default. Finally, these blocks will be stored in the object storage. At the same time, JuiceFS will store each file and its Chunks, Slices, Blocks and other metadata information in metadata engines. Learn more
Using JuiceFS, files will eventually be split into Chunks, Slices and Blocks and stored in object storage. Therefore, you will find that the source files stored in JuiceFS cannot be found in the file browser of the object storage platform. There is a chunks directory and a bunch of digitally numbered directories and files in the bucket. Don't panic, this is the secret of the high-performance operation of the JuiceFS!
To create a JuiceFS, you need the following 3 preparations:
- Redis database for metadata storage
- Object storage is used to store data blocks
- JuiceFS Client
Please refer to Quick Start Guide to start using JuiceFS immediately!
There is a command reference to see all options of the subcommand.
Using JuiceFS on Kubernetes is so easy, have a try.
Hadoop Java SDK
If you wanna use JuiceFS in Hadoop, check Hadoop Java SDK.
- Redis Best Practices
- Mount JuiceFS at Boot
- How to Setup Object Storage
- Cache Management
- Fault Diagnosis and Analysis
- FUSE Mount Options
- Sync Accounts between Multiple Hosts
- Using JuiceFS on Kubernetes
- Using JuiceFS on Windows
- S3 Gateway
JuiceFS passed all of the 8813 tests in latest pjdfstest.
All tests successful. Test Summary Report ------------------- /root/soft/pjdfstest/tests/chown/00.t (Wstat: 0 Tests: 1323 Failed: 0) TODO passed: 693, 697, 708-709, 714-715, 729, 733 Files=235, Tests=8813, 233 wallclock secs ( 2.77 usr 0.38 sys + 2.57 cusr 3.93 csys = 9.65 CPU) Result: PASS
Besides the things covered by pjdfstest, JuiceFS provides:
- Close-to-open consistency. Once a file is closed, the following open and read are guaranteed see the data written before close. Within same mount point, read can see all data written before it immediately.
- Rename and all other metadata operations are atomic guaranteed by Redis transaction.
- Open files remain accessible after unlink from same mount point.
- Mmap is supported (tested with FSx).
- Fallocate with punch hole support.
- Extended attributes (xattr).
- BSD locks (flock).
- POSIX record locks (fcntl).
JuiceFS provides a subcommand to run a few basic benchmarks to understand how it works in your environment:
$ ./juicefs bench /jfs Written a big file (1024.00 MiB): (113.67 MiB/s) Read a big file (1024.00 MiB): (127.12 MiB/s) Written 100 small files (102.40 KiB): 151.7 files/s, 6.6 ms for each file Read 100 small files (102.40 KiB): 692.1 files/s, 1.4 ms for each file Stated 100 files: 584.2 files/s, 1.7 ms for each file FUSE operation: 19333, avg: 0.3 ms Update meta: 436, avg: 1.4 ms Put object: 356, avg: 4.8 ms Get object first byte: 308, avg: 0.2 ms Delete object: 356, avg: 0.2 ms Used: 23.4s, CPU: 69.1%, MEM: 147.0 MiB
It shows JuiceFS can provide 10X more throughput than the other two, read more details.
It shows JuiceFS can provide significantly more metadata IOPS than the other two, read more details.
There is a virtual file called
.accesslog in the root of JuiceFS to show all the operations and the time they takes, for example:
$ cat /jfs/.accesslog 2021.01.15 08:26:11.003330 [uid:0,gid:0,pid:4403] write (17669,8666,4993160): OK <0.000010> 2021.01.15 08:26:11.003473 [uid:0,gid:0,pid:4403] write (17675,198,997439): OK <0.000014> 2021.01.15 08:26:11.003616 [uid:0,gid:0,pid:4403] write (17666,390,951582): OK <0.000006>
The last number on each line is the time (in seconds) current operation takes. You can use this directly to debug and analyze performance issues, or try
./juicefs profile /jfs to monitor real time statistics. Please run
./juicefs profile -h or refer to here to learn more about this subcommand.
Supported Object Storage
- Amazon S3
- Google Cloud Storage
- Azure Blob Storage
- Alibaba Cloud Object Storage Service (OSS)
- Tencent Cloud Object Storage (COS)
- QingStor Object Storage
- Ceph RGW
- Local disk
JuiceFS supports almost all object storage services. Learn more.
Who is using
It's considered as beta quality, the storage format is not stabilized yet. If you want to use it in a production environment, please do a careful and serious evaluation first. If you are interested in it, please test it as soon as possible and give us feedback.
You are welcome to tell us after using JuiceFS and share your experience with everyone. We have also collected a summary list in ADOPTERS.md, which also includes other open source projects used with JuiceFS.
- Stabilize storage format
- Support TiKV/FoundationDB as meta engine
Thank you for your contribution! Please refer to the CONTRIBUTING.md for more information.
JuiceFS by default collects anonymous usage data. It only collects core metrics (e.g. version number), no user or any sensitive data will be collected. You could review related code here.
These data help us understand how the community is using this project. You could disable reporting easily by command line option
$ ./juicefs mount --no-usage-report
JuiceFS is open-sourced under GNU AGPL v3.0, see LICENSE.
Why doesn't JuiceFS support XXX object storage?
JuiceFS already supported many object storage, please check the list first. If this object storage is compatible with S3, you could treat it as S3. Otherwise, try reporting issue.
Can I use Redis cluster?
The simple answer is no. JuiceFS uses transaction to guarantee the atomicity of metadata operations, which is not well supported in cluster mode. Sentinal or other HA solution for Redis are needed.
See "Redis Best Practices" for more information.
What's the difference between JuiceFS and XXX?
See "Comparison with Others" for more information.
For more FAQs, please see the full list.