-
Notifications
You must be signed in to change notification settings - Fork 27
Consider moving from master/slave terminology #2
Comments
Very, very +1 (and |
'master' and 'slave' are the buildbot terminology. |
Yeah, that would be tricky. You can always fork Buildbot and hope a simple text replacement would work |
@steveklabnik Primary/replica doesn't seem to fit, as there's a controller (the current "master") which completely controls the other instances (the current "slaves"), i.e. they're not replicas of the primary. |
@tbu- What about leader/follower? |
That sounds better. |
I think "leader/follower" works as a pretty much universal replacement for "master/slave". I don't do any Rust at work, but we've started to use this nomenclature for multi-server environments there. |
uwsgi uses emperor/vassal for some similar feature. "peon" is a great word too. but then i'm inclined towards colorful names :) |
leader/follower is pretty popular among projects making this particular change. |
@steveklabnik leader/follower seems correct in this case for me. |
For CI stuff in the past I've used "server/worker" or "server/builder". |
leader/follower seems more general than leader/builder though I like both |
Oh my, please check django/django#2692 |
coordinator/worker is probably what I'd use if I were building a CI system. |
Would suggest controller/worker, but +1 to coordinator/worker, too. |
Drupal decided on using |
A build system's naming scheme isn't describing the same thing as a On Wed, Feb 4, 2015 at 3:25 PM, Tim Plunkett notifications@github.com
"I disapprove of what you say, but I will defend to the death your right to |
+1 for leader / follower, given the context. |
|
http://trac.buildbot.net/ticket/2340 may also be of interest. |
primary/secondary? That's sort of what mongo does: Primary and replica would work, too, but that might be too specific in terms of function of the "non-primary" machine. Secondary is nicely general, if that matters. |
@zjjw Your terminology doesn't quite fit, it might fit for databases, but not for build servers. server/worker might fit. |
@reaperhulk I was in the process of writing a comment there when you posted the link 👍 |
We should avoid using "leader" in upper case or any other context where it could be construed as a title. |
slave -> worker above the rest of the suggestions. Perhaps master is all right with that change, trying to decide for myself. For the master:
Edit: ha! Marx's comments on the buildbot ticket are my exact potential issue with master / worker. |
I'm throwing in |
I think If it didn't make things even more confusing, I'd suggest something like |
CouchDB also switched to primary / replica, if I remember correctly: https://issues.apache.org/jira/browse/COUCHDB-2248 |
Although |
I prefer |
@tbi- describing the current "master" as a controller made me think controller/drone or controller/worker might be good. |
"Drone" is equally problematic in parts of the world ravaged by US military intervention. |
Thank you everyone for your suggestions. Given that we're not a database, I agree that
If upstream ends up rejecting this, we can re-open and see what we can do, but for now, dealing with them is the correct course of action. |
How about "gun" and "shovel"? "You see in this world there's two kinds of people, my friend. Those with loaded guns, and those who dig. You dig." |
This seems like an internal tool, but it might be a good idea to change from 'master/slave' to something less problematic.
I'm not familiar with this tool, but
primary
/replica
might work. (or leader/follower)@steveklabnik @brson, thoughts?
The text was updated successfully, but these errors were encountered: