[
https://issues.apache.org/jira/browse/SOLR-14702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170569#comment-17170569
]
Marcus Eagan commented on SOLR-14702:
-------------------------------------
{quote}I think this is really off? Definitely alerts will be different. As we
both agreed, the architectures are different and so are the things to
monitor/alert on. This is no different than having Solr in SolrCloud mode
running in completely different infrastructure (say, Kubernetes vs bare metal),
the alerts and actions to take are different. If you have enough clusters to
need a "reminder" of the mode they are in running on you most likely have a
tool to track it.
{quote}
My point was that people will take logical shortcuts to comprehend, looking for
keywords and deductions. SolrCloud on Kubernetes vs bare metal is
non-analagous, especially considering you can run Kubernetes on bare metal.
Kubernetes is just server orchestration software. You can put it on EC2,
baremetal, or wherever you can find 4 GB of RAM and 2 CPUs.
Regardless of the tracking/alerting tool, the output of it should be as obvious
as possible. Context switching with conflicting terms is a recipe for
production outages.
> Remove Master and Slave from Code Base and Docs
> -----------------------------------------------
>
> Key: SOLR-14702
> URL: https://issues.apache.org/jira/browse/SOLR-14702
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (9.0)
> Reporter: Marcus Eagan
> Priority: Critical
> Attachments: SOLR-14742-testfix.patch
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> Every time I read _master_ and _slave_, I get pissed.
> I think about the last and only time I remember visiting my maternal great
> grandpa in Alabama at four years old. He was a sharecropper before WWI, where
> he lost his legs, and then he was back to being a sharecropper somehow after
> the war. Crazy, I know. I don't know if the world still called his job
> sharecropping in 1993, but he was basically a slave—in America. He lived in
> the same shack that his father, and his grandfather (born a slave) lived in
> down in Alabama. Believe it or not, my dad's (born in 1926) grandfather was
> actually born a slave, freed shortly after birth by his owner father. I never
> met him, though. He died in the 40s.
> Anyway, I cannot police all terms in the repo and do not wish to. This
> master/slave shit is archaic and misleading on technical grounds. Thankfully,
> there's only a handful of files in code and documentation that still talk
> about masters and slaves. We should replace all of them.
> There are so many ways to reword it. In fact, unless anyone else objects or
> wants to do the grunt work to help my stress levels, I will open the pull
> request myself in effort to make this project and community more inviting to
> people of all backgrounds and histories. We can have leader/follower, or
> primary/secondary, but none of this Master/Slave nonsense. I'm sick of the
> garbage.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
