Thanks for this, I missed it when it came through originally.
My next question is where is the detailed documentation for storage
options? The 'Formatting and Mounting Bricks' section of the
documentation
seems to give an example of a single drive mounted as a thin volume. Where
is the documentation for the benefits/drawbacks of different options, RAID
configs, requirements vs recommendations?
For example, in my case of having two SSDs, valid questions might be:
- what's the best configuration for performance
- can I create a striped LV to use as a brick or should I just be
creating two bricks from the two SSDs?
- what are the considerations for being able to expand the pool at a later
stage?
I can't find any sort of discussion on these sort of questions that would
be asked in a planning phase.
Thanks.
On Mon, Feb 17, 2020 at 10:18 AM Strahil Nikolov <hunter86_bg at
yahoo.com>
wrote:
> On February 17, 2020 9:10:42 AM GMT+02:00, Shareef Jalloq <
> shareef at jalloq.co.uk> wrote:
> >Hi there,
> >
> >New user here and I'm still reading documentation but had a
question
> >regarding suitability of Gluster for different applications. I've
just
> >read
> >the note that states Gluster isn't suitable for things like a NoSQL
DB
> >and
> >wanted to know more.
> >
> >So on the DB front, what's the technical reason for this? High iops
to
> >small files? Have I missed the documentation for this?
> >
> >What I'm trying to do is build a HA Docker Swarm on top of Gluster.
I
> >was
> >assuming I could just mount the Gluster volume to /mnt/persistent_data,
> >or
> >whatever, and use Docker Volumes to map into the containers? Are there
> >reasons for not doing this?
> >
> >One of the services I need to run is Git LFS which uses a DB to store
> >large/binary files and uses file locking. Is this an issue?
> >
> >Thanks, Shareef.
>
> Hi Shareef,
>
> Actually there is no problem to run a DB ontop of gluster.
> There is a set of predefined settings for db workload:
>
> '[root at host groups]# ll /var/lib/glusterd/groups/db-workload
> -rw-r--r--. 1 root root 337 Oct 16 13:57
> /var/lib/glusterd/groups/db-workload
>
> The only limit is the IOPS of your disks and the bandwidth between the
> clients and nodes. Gluster supports RDMA, so lattency can be kept to the
> minimum and with NVMEs , you can reach (and even exceed) performance of
> most storages while having the ability to scale-out as per your needs.
> For high performance , you should consider using libgfapi or NFS Ganesha.
>
>
> Best Regards,
> Strahil Nikolov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20200223/8bd0e092/attachment.html>