-
Notifications
You must be signed in to change notification settings - Fork 188
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
More on Global Locks #290
Comments
|
If various ideas for metadata footprint and scalability are still being considered BeeGFS (formerly FhGFS) does a pretty good job in this respect. |
@borkd, BeeGFS is proprietary so they can claim pretty much anything they want and you won't be able to verify their claims. Let's waste no time for proprietary systems, shall we? |
Now that MooseFS seems to have global locks (https://moosefs.com/products/overview.html) and given their code is GPL, should we expect to see this soon in LizardFS? Global locks would be great for running CTDB+Samba to avoid having to use GlusterFS or NFS for the CTDB lock area.
Also can the masters still be managed by Corosync and Pacemaker until the new HA stuff is finalised? Is there any easy recipe for this around? I've looked across the repo and all the info on master HA is very confusing and often conflicting.
One more thing - a wishlist item - Metadata sharding ;-) I know that metadata stuff is really hard to do right (see CephFS!) so it may just be a pipedream. Does open the opportunity to have billions or trillions of files/chunks without paying for an 8-socket Xeon box,,,
Thanks
Alex
The text was updated successfully, but these errors were encountered: