Thing is, we can get a cluster wide lock when needed through zookeeper. It's collection cluster wide lock BTW most of the time (or locks on shards or replicas of a collection). We could already today (in master) have multiple Overseer and distribute (partition) the collections to them...
In 8x we still need cluster wide locks for /clusterstate.json based operations. Ilan Le ven. 19 juin 2020 à 20:52, Jan Høydahl <jan....@cominvent.com> a écrit : > supervisor > > The name change should probably happen as part of the major overseer > overhaul that is planned. Perhaps there won’t be much left of the overseer > if more operations can be done without a cluster-wide lock? > > Jan > > > 19. jun. 2020 kl. 20:03 skrev Walter Underwood <wun...@wunderwood.org>: > > > > I just split this off with a different subject line for the “overseer” > discussion. > > That seems independent of the other choices. > > > > I’ve heard these suggestions: > > > > * orchestrator > > * director > > * coordinator > > * cluster manager > > * manager > > > > There is a thing called “process orchestration” which is at a higher > level than > > what the overseer does. It might be something like all the customer > interactions > > in a billing process. That usage might be confusing for the term > “orchestrator”. > > > > wunder > > Walter Underwood > > wun...@wunderwood.org > > http://observer.wunderwood.org/ (my blog) > > > >> On Jun 18, 2020, at 10:44 PM, Thomas Corthals <tho...@klascement.net> > wrote: > >> > >> Since "overseer" is also problematic, I'd like to propose > "orchestrator" as > >> an alternative. > >> > >> Thomas > > > >
