Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MooseFS 3.x Erasure Code Support #560

Open
anon314159 opened this issue Dec 12, 2023 Discussed in #558 · 0 comments
Open

MooseFS 3.x Erasure Code Support #560

anon314159 opened this issue Dec 12, 2023 Discussed in #558 · 0 comments

Comments

@anon314159
Copy link

Discussed in #558

Originally posted by anon314159 December 11, 2023
Hello,

I just started playing around with MooseFS in one of my development environments and absolutely fell in love with it. From an experience perspective I have deployed multple Ceph and GlusterFS peta-scale clusters over the past six years. So my familiarity and comfort level with distributed filesystems is pretty high. I digress, while my initial experience with MooseFS has been very good, one glaring issue pops up and that is the lack of erasure code support makes it unusable in large scale deployments due to the massive waste of space caused by replication of data assigned via storage goals. While I'm new to MooseFS and haven't played around with the extensive configuration options for storage classes, not enabling or allowing EC in the free versions seems like "pricing yourself out of the market" against other open source distributed file systems. More to the point, are there any plans of adding erasure codes to the GPL version? Or better yet, am I simply missing something from the configuration options that would enable this feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant