Patch to support Scalable CTDB

[Partha Sarathi]

Ok. My concern is when you have common Ctdb running across cluster with
different file spaces keeping the locking.tdb replicated for all file opens
doesn’t seems to be worth.

So we decided to split the ctdb along with the file space to keep them
isolated and not interfering with other subcluster. But as I said we needed
the single global namespace for user and we have to keep secrets.tdb
consistent across all the nodes irrespective of different filespace.

—Partha
On Mon, Apr 30, 2018 at 2:46 AM Ralph Böhme <slow at samba.org> wrote:

> On Mon, Apr 30, 2018 at 08:43:51AM +0200, Volker Lendecke via
> samba-technical wrote:
> > On Sun, Apr 29, 2018 at 10:29:51AM -0700, Partha Sarathi via
> samba-technical wrote:
> > >      * Clustered locking.tdb record becomes "hot", bouncing between
> nodes
> > > >>>>>>> This particular reason "itched me" :-)
> >
> > Is that really solved by partitioning of the ctdb cluster? I could
> > imagine that if you share the same file space you will see broken
> > locking by subcluster A not seeing the locks of subcluster B. If you
> > separate out the filespaces, you don't win much except less nodes
> > beating the same files. Does that really gain enough performance?
>
> also, I guess partitioning the filespace should be possible without
> partitioning
> the cluster at the ctdb level at all.
>
> -slow
>
> --
> Ralph Boehme, Samba Team       https://samba.org/
> Samba Developer, SerNet GmbH   https://sernet.de/en/samba/
> GPG Key Fingerprint:           FAE2 C608 8A24 2520 51C5
>                                59E4 AA1E 9B71 2639 9E46
>
-- 
Thanks & Regards
-Partha