Did you try disperse volume? It may work your workload I think.
We are using disperse volumes for archive workloads with 2GB files and
I did not encounter any problems.
On Mon, Sep 17, 2018 at 1:43 AM Ashayam Gupta
<ashayam.gu...@alpha-grep.com> wrote:
>
> Hi All,
>
> We are currently using glusterfs for storing large files with write-once and
> multiple concurrent reads, and were interested in understanding one of the
> features of glusterfs called sharding for our use case.
>
> So far from the talk given by the developer
> [https://www.youtube.com/watch?v=aAlLy9k65Gw] and the git issue
> [https://github.com/gluster/glusterfs/issues/290] , we know that it was
> developed for large VM images as use case and the second link does talk about
> a more general purpose usage , but we are not clear if there are some issues
> if used for non-VM image large files [which is the use case for us].
>
> Therefore it would be helpful if we can have some pointers or more
> information about the more general use-case scenario for sharding and any
> shortcomings if any , in case we use it for our scenario which is non-VM
> large files with write-once and multiple concurrent reads.Also it would be
> very helpful if you can suggest the best approach/settings for our use case
> scenario.
>
> Thanks
> Ashayam Gupta
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
