e.org
Subject: Re: Getting rid of Master/Slave nomenclature in Solr
Here is some of the work I did to remedy this effort before I knew about this
email:
https://github.com/apache/lucene-solr/pull/1712
https://issues.apache.org/jira/browse/SOLR-14702page=com.atlassian.jira.plugin.system.issuetabp
Here is some of the work I did to remedy this effort before I knew about this
email:
https://github.com/apache/lucene-solr/pull/1712
https://issues.apache.org/jira/browse/SOLR-14702page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=17169865
It makes me sick
Time to decouple from the weighty semantics of human experience and look to
nature?
queens/workers/drones/swarms?
On Wed, 17 Jun 2020 at 20:38, Anshum Gupta wrote:
> Hi everyone,
>
> Moving a conversation that was happening on the PMC list to the public
> forum. Most of the following is just
First off: Forgive me if my comments/questions are redundent or uninformed
bsaed o nthe larger discussion taking place. I have not
caught up on the whole thread before replying -- but that's solely based
on a lack of time on my part, not a lack of willingness to embrace this
change.
>From
Actually, the term “master” is a problem, so master/follower doesn’t work.
GitLab is renaming the master branch to main.
Rice University renamed College Masters to College Magisters in 2017.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jun 18, 20
he term "master" is causing
> > concern all by itself. If we're going to make the change anyway, it might
> > be best to get it over with and pick the most appropriate terminology we
> > can agree upon, rather than trying to minimize the amount of change. It's
> going to be backward breaking anyway, so we might as well do it all now
> rather than risk having to go through two separate breaking changes at
> different points in time.
> >
> > - Demian
> >
> > -Original Message-
> > From: Noble Paul
> >
Primary / satellite?
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc
Description: PGP signature
; having to go through two separate breaking changes at different points in
> time.
>
> - Demian
>
> -Original Message-
> From: Noble Paul
> Sent: Thursday, June 18, 2020 1:51 AM
> To: solr-user@lucene.apache.org
> Subject: [EXTERNAL] Re: Getting rid of Master/Slav
s at different points in time.
- Demian
-Original Message-
From: Noble Paul
Sent: Thursday, June 18, 2020 1:51 AM
To: solr-user@lucene.apache.org
Subject: [EXTERNAL] Re: Getting rid of Master/Slave nomenclature in Solr
Looking at the code I see a 692 occurrences of the word "slave&
+1 Noble and Ilan !!
On Thu, Jun 18, 2020 at 7:51 AM Noble Paul wrote:
> Looking at the code I see a 692 occurrences of the word "slave".
> Mostly variable names and ref guide docs.
>
> The word "slave" is present in the responses as well. Any change in
> the request param/response payload is
Looking at the code I see a 692 occurrences of the word "slave".
Mostly variable names and ref guide docs.
The word "slave" is present in the responses as well. Any change in
the request param/response payload is backward incompatible.
I have no objection to changing the names in ref guide and ot
Would master/follower work?
Half the rename work while still getting rid of the slavery connotation...
On Thu 18 Jun 2020 at 07:13, Walter Underwood wrote:
> > On Jun 17, 2020, at 4:00 PM, Shawn Heisey wrote:
> >
> > It has been interesting watching this discussion play out on multiple
> open
> On Jun 17, 2020, at 4:00 PM, Shawn Heisey wrote:
>
> 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.
Yes, it is nice
Master/slave is not going away in our company. That cluster has zero downtime
in five years. I can’t say that about our Solr Cloud clusters.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jun 17, 2020, at 9:36 PM, Noble Paul wrote:
>
> I really do
I really do not see a reason why a master/slave terminology is a problem.
We do not have slavery anywhere in the world. Should we also remove it from
the dictionary?
The old mode is going to go away anyway. Why waste time bikeshedding on
this?
On Thu, Jun 18, 2020, 12:04 PM Trey Grainger wrote:
@Shawn,
Ok, yeah, apologies, my semantics were wrong.
I was thinking that a TLog replica is a follower role only and becomes an
NRT replica if it gets elected leader. From a pure semantics standpoint,
though, I guess technically the TLog replica doesn't "become" an NRT
replica, but just "acts the
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
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 wrote:
On
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 a
Master/slave is not just two roles, but a kind of cluster. I really don’t think
“Standalone” captures the non-Cloud cluster. Nobody in Chegg would
have any idea that “standalone” meant “no Zookeeper”.
I’ve never thought that master/slave accurately described the traditional
replication model, but
Sorry:
>
> but I maintain that leader vs. follower behavior is inconsistent here.
Sorry, that should have said "I maintain that leader vs. follower behavior
is consistent here."
Trey Grainger
Founder, Searchkernel
https://searchkernel.com
On Wed, Jun 17, 2020 at 6:03 PM Trey Grainger wrote:
>
Hi Walter,
>In Solr Cloud, the leader knows about each follower and updates them.
Respectfully, I think you're mixing the "TYPE" of replica with the role of
the "leader" and "follower"
In SolrCloud, only if the TYPE of a follower is NRT or TLOG does the leader
push updates those followers.
When
+1 for simplifying and using the Leader/Follower Terminology. Our company
operates both SolrCloud, Standalone Solr, and Master/Slave Configurations,
outside of the Solr Developer community, it's painful and confusing to talk
about Master/Slave and Leader/Replica. It would be easier if we had the
fo
But they are not the same. In Solr Cloud, the leader knows about each
follower and updates them. In standalone, the master has no idea that
slaves exist until a replication request arrives.
In Solr Cloud, the leader is elected. In standalone, that role is fixed at
config load time.
Looking ahead
+1 for Leader-Follower. How about Publisher-Subscriber?
On Wed, Jun 17, 2020 at 5:19 PM Rahul Goswami wrote:
> +1 on avoiding SolrCloud terminology. In the interest of keeping it obvious
> and simple, may I I please suggest primary/secondary?
>
> On Wed, Jun 17, 2020 at 5:14 PM Atita Arora wrot
I guess I don't see it as polysemous, but instead simplifying.
In my proposal, the terms "leader" and "follower" would have the exact same
meaning in both SolrCloud and standalone mode. The only difference would be
that SolrCloud automatically manages the leaders and followers, whereas in
standalo
+1 on avoiding SolrCloud terminology. In the interest of keeping it obvious
and simple, may I I please suggest primary/secondary?
On Wed, Jun 17, 2020 at 5:14 PM Atita Arora wrote:
> I agree avoiding using of solr cloud terminology too.
>
> I may suggest going for "prime" and "clone"
> (Short an
I agree avoiding using of solr cloud terminology too.
I may suggest going for "prime" and "clone"
(Short and precise as Master and Slave).
Best,
Atita
On Wed, 17 Jun 2020, 22:50 Walter Underwood, wrote:
> I strongly disagree with using the Solr Cloud leader/follower terminology
> for non-C
I strongly disagree with using the Solr Cloud leader/follower terminology
for non-Cloud clusters. People in my company are confused enough without
using polysemous terminology.
“This node is the leader, but it means something different than the leader
in this other cluster.” I’m dreading that conv
Proposal:
"A Solr COLLECTION is composed of one or more SHARDS, which each have one
or more REPLICAS. Each replica can have a ROLE of either:
1) A LEADER, which can process external updates for the shard
2) A FOLLOWER, which receives updates from another replica"
(Note: I prefer "role" but if othe
31 matches
Mail list logo
