|
Krutika, Thanks for letting me know that this is already in works. The use case is to provide a Scaleout NAS for large media files.
Thanks and Regards, Ram From: Krutika Dhananjay [mailto:kdhananj@xxxxxxxxxx]
Hi, Work is in progress for this (and going a bit slow at the moment because of other priorities). At the moment we support sharding only for VM image store use-case - most common large file + single writer use case we know of. Just curious, what is the use case where you want to use shard+EC? -Krutika On Thu, May 4, 2017 at 4:05 PM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote: +Krutika Krutika started work on this. But it is very long term. Not a simple thing to do. On Thu, May 4, 2017 at 3:53 PM, Ankireddypalle Reddy <areddy@xxxxxxxxxxxxx> wrote: Pranith, Thanks. Is there any work in progress to add this support. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu@xxxxxxxxxx]
On Thu, May 4, 2017 at 3:43 PM, Ankireddypalle Reddy <areddy@xxxxxxxxxxxxx> wrote: Pranith, Thanks. Does it mean that a given file can be written by only one client at a time.
If multiple clients try to access the file in write mode, does it lead to any kind of data inconsistencies. We only tested it for single writer cases such as VM usecases. We need to bring in transaction framework for sharding to work with multiple writers.
Pranith ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
-- Pranith ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
