I agree with Shawn that the top contenders so far (from my perspective) are "primary/secondary" and "publisher/subscriber", and agree with Walter that whatever term pair is used should ideally be usable *as a pair* (to identify a cluster type) in addition to individually (to identify the individual roles in that cluster).
To take the "bikeshedding" metaphor in another direction, I'd submit "hub/spoke"? It's a little overloaded, but afaict mainly in domains other than cluster architecture. It's very usable as a pair; it manages to convey the singular nature of the "hub" and the equivalent/final nature of the "spokes" in a way that "primary/secondary" doesn't really; and it avoids implying an active role in cluster maintenance for the "hub" (cf. "publisher", which could be misleading in this regard). Michael On Wed, Jun 17, 2020 at 9:12 PM Scott Cote <scottcc...@yahoo.com.invalid> wrote: > > Perhaps Apache could provide a nomenclature suggestion that the projects > could adopt. This would stand well for the whole Apache community in > regards to BLM. > My two cents as a “user” > Good luck. > > > Sent from Yahoo Mail for iPhone > > > On Wednesday, June 17, 2020, 6:00 PM, Shawn Heisey <apa...@elyograg.org> > wrote: > > On 6/17/2020 2:36 PM, Trey Grainger wrote: > > 2) TLOG - which can only serve in the role of follower > > This is inaccurate. TLOG can become leader. If that happens, then it > functions exactly like an NRT leader. > > I'm aware that saying the following is bikeshedding ... but I do think > it would be as mistake to use any existing SolrCloud terminology for > non-cloud deployments, including the word "replica". The top contenders > I have seen to replace master/slave in Solr are primary/secondary and > publisher/subscriber. > > It has been interesting watching this discussion play out on multiple > open source mailing lists. On other projects, I have seen a VERY high > level of resistance to these changes, which I find disturbing and > surprising. > > Thanks, > Shawn > > >
