Looks like mountpoint-s3 is the way to go. If we adopt mountpoint-s3, we can also leverage AWS's CSI driver https://github.com/awslabs/mountpoint-s3-csi-driver?tab=readme-ov-file Would be interesting to see how well it works for Ozone to be mounted as a kubernetes storage.
On Fri, Jul 11, 2025 at 5:52 PM Siyao Meng <si...@apache.org> wrote: > +1 > > mountpoint-s3 sounds promising. > > s3fs-fuse has lower performance than Goofys but might have the lowest > friction as a replacement. > > -Siyao > > On Mon, Jul 7, 2025 at 11:02 AM Abhishek Pal < > pal.abhishek03012...@gmail.com> > wrote: > > > +1 on looking for a replacement since goofys is not being maintained. > > JuiceFS seems to introduce the problem of having to maintain an extra > > component for metadata which might come back to bite us, unless we let > > users setup and manage it by themselves. > > > > Maybe understanding what POSIX operations we absolutely want would be a > > good first step since mountpoint-s3 seems like a good alternative > > (considering the performance hit that might be seen with s3fs-fuse) > > > > On Mon, 7 Jul 2025 at 20:22, Ethan Rose <er...@apache.org> wrote: > > > > > +1 for finding a goofys replacement. All of s3fs-fuse, mountpoint-s3, > and > > > juicefs are probably worth testing since they seem to have different > use > > > cases. mountpoint-s3 and s3fs are most similar to goofys in that the > > > namespace exposed matches what is stored in Ozone but some posix > > operations > > > are not supported. My understanding is that s3fs-fuse is more posix > than > > > mountpoint-s3 at the cost of performance. Juicefs is fully posix but > the > > > tradeoff is it stores metadata in a separate DB, so data written > through > > > juicefs is not usable with just core Ozone. > > > > > > Ethan > > > > > > On Mon, Jul 7, 2025 at 5:23 AM Sammi Chen <sammic...@apache.org> > wrote: > > > > > > > +1, goofys is not stable after hours of running, especially in the > > > > continuous file write case. > > > > We'd better benchmarking these new candidates. > > > > > > > > BTW, I have heard of one JuiceFS + Ozone case, which seems running > > well. > > > > > > > > Sammi > > > > > > > > On Sun, 6 Jul 2025 at 15:29, Tsz-Wo Nicholas Sze <szets...@gmail.com > > > > > > wrote: > > > > > > > > > +1 If goofys is unmaintained, we should find a replacement. > > > > > > > > > > Tsz-Wo > > > > > > > > > > On Tue, Jul 1, 2025 at 11:46 AM Wei-Chiu Chuang < > weic...@apache.org> > > > > > wrote: > > > > > > > > > > > 1. HDDS-13356 < > https://issues.apache.org/jira/browse/HDDS-13356 > > > > > > > > > > > > > > > Goofys is a s3 fuse client. We rely on goofys to mount s3 locally > > and > > > > our > > > > > > ozone csi driver depends on goofys. Ozone-docker-runner includes > > > > goofys: > > > > > > > > > > > > However, goofys looks unmaintained now. No new releases in 4 > years. > > > > > > > > > > > > In the meantime, there are better S3 fuse clients: for example, > > > > > > https://github.com/awslabs/mountpoint-s3, JuiceFS: > > > > > https://juicefs.com/en/ > > > > > > s3 > > > > > > fuse: https://github.com/s3fs-fuse/s3fs-fuse > > > > > > > > > > > > We should consider replacing goofys with either option. Thoughts? > > > > > > > > > > > > > > > > > > > > >
