Since "overseer" is also problematic, I'd like to propose "orchestrator" as
an alternative.
Thomas
Op vr 19 jun. 2020 04:34 schreef Walter Underwood :
> We don’t get to decide whether “master” is a problem. The rest of the world
> has already decided that it is a problem.
>
> Our task is to
Trying think of a term that both fresh (and yet sort of standard already) and
appropriate: how about IndexFetcher instead of "Slave"? And then "Master" could
be "FetchedIndex" or "FetchedSource"
I think it could be beneficial to broaden the range of candidates.
I sometimes describe them as tightly-coupled and loosely-coupled. There is a
vast
difference in the amount of shared state in the two kinds of clusters. Old
school
clusters are essentially a REST system. The primary server knows nothing
about the leeches. The replication only assumes that the
>
> Let’s instead find a new good name for the cluster type. Standalone kind
> of works
> for me, but I see it can be confused with single-node.
Yeah, I've typically referred to it as "standalone", but I don't think it's
descriptive enough. I can see why some people have been calling it
We don’t get to decide whether “master” is a problem. The rest of the world
has already decided that it is a problem.
Our task is to replace the terms “master” and “slave” in Solr.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jun 18, 2020, at
I agree with Phill, Noble and Ilan above. The problematic term is "slave"
(not master) which I am all for changing if it causes less regression than
removing BOTH master and slave. Since some people have pointed out Github
changing the "master" terminology, in my personal opinion, it was not a
Master - Worker
Master - Peon
Master - Helper
Master - Servant
The term that is not wanted is “slave’. The term “master” is not a problem IMO.
> On Jun 18, 2020, at 3:59 PM, Jan Høydahl wrote:
>
> I support Mike Drob and Trey Grainger. We shuold re-use the leader/replica
> terminology from
Have you tried starting each node with -Dsolr.disable.shardsWhitelist=true to
revert back to old behavior?
Jan
> 18. jun. 2020 kl. 17:23 skrev Ray W :
>
> Hi Everyone,
>
> We upgraded to solr 6.6.6 and a recurring error shows up as "shards
> parameter value contained values not in the shards
I support Mike Drob and Trey Grainger. We shuold re-use the leader/replica
terminology from Cloud. Even if you hand-configure a master/slave cluster
and orchestrate what doc goes to which node/shard, and hand-code your shards
parameter, you will still have a cluster where you’d send updates to the
compile(group: 'org.springframework.boot',name:
'spring-boot-starter-web',version: '2.2.6.RELEASE')
compile(group: 'javax.inject', name: 'javax.inject', version:'1')
compile(group: 'javax.ws.rs', name: 'javax.ws.rs-api', version: '2.1.1')
compile group: 'ch.qos.logback', name: 'logback-core',
: Subject: Does 8.5.2 depend on 8.2.0
No. The code certainly doesn't, but i suppose it's possible some metadata
somewhere in some pom file may be broken?
: My build.gradle has this:
: compile(group: 'org.apache.solr', name: 'solr-solrj', version:'8.5.2')
: No where is there a reference to
I use gradle to build my project. I noticed that in the build the jar it is
using is 8.2.0. I don’t include that anywhere.
I clear my grade cache and rebuild and I see this:
$find . -name "solr*"
./modules-2/metadata-2.71/descriptors/org.apache.solr/solr-parent
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
Hi Everyone,
We upgraded to solr 6.6.6 and a recurring error shows up as "shards
parameter value contained values not in the shards whitelist". I have
attached the error log as well as configurations in solr.xml and
solrconfig.xml. Solr 6.6 documentations doesn't cover setting up a
shards
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,
I personally think that using Solr cloud terminology for this would be fine
with leader/follower. The leader is the one that accepts updates, followers
cascade the updates somehow. The presence of ZK or election doesn’t really
change this detail.
However, if folks feel that it’s confusing, then I
While on the topic of renaming roles, I'd like to propose finding a better
term than "overseer" which has historical slavery connotations as well.
Director, perhaps?
John Gallagher
On Thu, Jun 18, 2020 at 8:48 AM Jason Gerlowski
wrote:
> +1 to rename master/slave, and +1 to choosing
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
+1 to rename master/slave, and +1 to choosing terminology distinct
from what's used for SolrCloud. I could be happy with several of the
proposed options. Since a good few have been proposed though, maybe
an eventual vote thread is the most organized way to aggregate the
opinions here.
I'm less
Regarding people having a problem with the word "master" -- GitHub is changing
the default branch name away from "master," even in isolation from a "slave"
pairing... so the terminology seems to be falling out of favor in all contexts.
See:
Hello solr-fellows,
i'm currently implementing the MoreLikeThis Feature in an e-commerce platform.
I setup my solr.MoreLikeThisHandler in my solrconfig.xml like this:
aid, eans, desclong
list
true
10
aid, eans, desclong
0
Running the following command
Thanks, just created SOLR-14581 as an entry point.
And sure, beers sound good! ;-)
On 17/06/2020 23:13, Erick Erickson wrote:
> Please raise a JIRA and attach your patch to that….
>
> Best,
> Erick
>
> P.S. Buy me some beers sometime if we’re even in the same place...
>
>> On Jun 17, 2020, at
+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
It seems like my Email got lost the first time, so I'll give it a second
try.
-- Forwarded message -
From: Razvan-Daniel Mihai
Date: Tue, Jun 16, 2020 at 3:28 PM
Subject: SolrCloud creates the data folder in solr.data.home instead of
solr.core.name
To:
Hello,
I run a
Hi Florian,
I don’t know the answer to your specific question, but I would like to suggest
a different approach. Excuse me in advance, I usually hate suggesting different
approaches.
The reason why I suggest a different approach is because logging via HTTP can
be blocking a thread e.g. until
25 matches
Mail list logo
