3:03 a.m.
On Tue, May 21, 2019 at 12:47:32PM +0530, Suhrud Patankar wrote:
We want to run two separate Ganesha processes on one node. (Using
2.7.1 code level)
The config params "Bind_Addr" and "Dbus_Name_Prefix" work as
expected
to isolate the two instances.
So we have each process binding to separate network interface and gets
its own DBus bus-name.
They need to serve different file systems, so not much worry about the
cache consistency between them.
Is there any specific area we need to worry about? Has anyone tried
similar setup?
Yes, I tried it in a cluster of storage gateways with one ganesha daemon
per virtual ip and automatic failover via ctdb, against a ceph backend.
Short version: Locking will be a problem.
(It's a problem to begin with, but beyond that.)
NFSv3 locking is hopeless, the rpc daemons are not aware of multiple
processes, they will mess each other up and no amount of namespacing
or containerizing will convince it otherwise.
NFSv4 depends on the client. We had all kinds of vague issues depending
on type of workload. A vmware client had no apparent problems whatsoever,
others did.
I built this on ganesha 2.7.1. Currently running 2.7.3 on a few test vips
but we couldn't get it stable enough for production use.
There was the odd crashing ganesha daemon if I was really hammering it,
but other than the locking issue it was looking pretty good. Performed
well, too.
--
Michel Buijsman