3 ms·
before you want to use it in your project, make sure to have a look at the code - their codebase is pretty much comment free, very little number of tests. Other
by dis-sys 6y ago
before you want to use it in your project, make sure to have a look at the code - their codebase is pretty much comment free, very little number of tests. Other than the marketing term "posix file system", there is not any proof on such claim.
I am also not sure how it is a "distributed" file system given its storage is entirely done by S3. Should I call my backup program that backups my data to S3 every night a "distributed system"? When running on top of Redis, it explicitly mentions that Redis cluster is not supported. I haven't used Redis for many years, did I miss something here? A "distributed" file system built on top of a single instance of Redis? Sounds not very "distributed" to me.
- Benjamin_Dobell 6y agoLooks like they run against a whole suite (several actually) of third-party tests: https://github.com/juicedata/juicefs/blob/main/fstests/Makefile https://github.com/juicedata/juicefs/blob/main/fstests/Makef...
- daviesliu 6y agoSince POSIX is so complicated that we would not trust the test we wrote to prove the compatibility. So we use several third-party test suite, including fsx, pjdfstest, fsracer, flock. We also use third-party tools for benchmark, fio, mdtest and others.
- daviesliu 6y agoThe architect of JuiceFS is very close to GFS, which use a single node master for many years, even now. Since Redis is only responsible for metadata, a single node can serve hundreds of millions of files, and tens of thousands of IOPS, that should be enough for many use cases. The term `distributed`, means that JuiceFS is not a `local` file system, or can only be used by single machine. JuiceFS should be qualified as distributed system, even the core part is the client, which could be used by many machines in the same time.
- q3k 6y ago> The architect of JuiceFS is very close to GFS, which use a single node master for many years, even now. GFS has since evolved into Colossus which doesn't have this architecture limitation.
- daviesliu 6y agoBased on some information found on internet, Colossus is built on top of GFS, which use BigTable (or Spanner) as the meta store, and the BigTable still use GFS. The recent GFS may have multiple masters[1], but they are separate namespace, similar to HDFS federation. [1] https://queue.acm.org/detail.cfm?id=1594206 https://queue.acm.org/detail.cfm?id=1594206