+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 <are...@commvault.com>
wrote:

> Pranith,
>
>                  Thanks. Is there any work in progress to add this support.
>
>
>
> Thanks and Regards,
>
> Ram
>
> *From:* Pranith Kumar Karampuri [mailto:pkara...@redhat.com]
> *Sent:* Thursday, May 04, 2017 6:17 AM
>
> *To:* Ankireddypalle Reddy
> *Cc:* Gluster Devel (gluster-devel@gluster.org); gluster-us...@gluster.org
> *Subject:* Re: [Gluster-devel] Enabling shard on EC
>
>
>
>
>
>
>
> On Thu, May 4, 2017 at 3:43 PM, Ankireddypalle Reddy <are...@commvault.com>
> 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.
>
>
>
>
>
> Thanks and Regards,
>
> Ram
>
> *From:* Pranith Kumar Karampuri [mailto:pkara...@redhat.com]
> *Sent:* Thursday, May 04, 2017 6:07 AM
> *To:* Ankireddypalle Reddy
> *Cc:* Gluster Devel (gluster-devel@gluster.org); gluster-us...@gluster.org
> *Subject:* Re: [Gluster-devel] Enabling shard on EC
>
>
>
> It is never been tested. That said, I don't see any missing pieces that we
> know of for it to work. Please note that sharding works only for single
> writer cases at the moment. Do let us know if you find any problems and we
> will fix them.
>
>
>
> On Wed, May 3, 2017 at 2:17 PM, Ankireddypalle Reddy <are...@commvault.com>
> wrote:
>
> Hi,
>
>       Are there any known negatives of enabling shard on EC. Is this a
> recommended configuration?.
>
>
>
> Thanks and Regards,
>
> Ram
>
>
>
>
>
> ***************************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-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
>
>
>
> --
>
> 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."
> **********************************************************************
>



-- 
Pranith
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Reply via email to