There has been a deadlock problem in the past where both the knfs
module and the fuse module each need more memory to satisfy a fop
and neither can acquire that memory due to competing locks. This
caused an infinite wait. Not sure if anything was ever done in the
kernel to remedy that.
On 03/07/18 11:50, Ben Mason wrote:
Hello,
I'm designing a 2-node, HA NAS that must support NFS. I had
planned on using GlusterFS native NFS until I saw that it is
being deprecated. Then, I was going to use GlusterFS +
NFS-Ganesha until I saw that the Ganesha HA support ended
after 3.10 and its replacement is still a WIP. So, I landed on
GlusterFS + kernel NFS + corosync & pacemaker, which seems
to work quite well. Are there any performance issues or other
concerns with using GlusterFS as a replication layer and
kernel NFS on top of that?
Thanks!
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users