[Gluster-users] Docker swarm on top of Replica 3?

[Strahil Nikolov]

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