Re: Removing references to Master

We maybe don't need to litigate this one again. I do think this point of view is legitimate, as is the point of view that 'master' is inextricably linked to 'master/slave' as an unfortunate term of art; it did not originate in reference to mastery of a skill but of another entity. Even if one viewe

Re: Removing references to Master

Hi, I am afraid I have to differ on this if I may. This is the gist of it. The term master has been a part of English and English speaking culture for a very long time. Unlike " slave" this term "master" has no connotation to anything related to race, creed and so forth. It is widely used in the

Re: Removing references to Master

Hey everyone, Looking at this again since we cut spark 3.2 branch thinking this might be something to target for Spark 3.3. Based on the feedback, I'd like to propose using "Leader" to replace "Master". If there are objections to this please let me know in the next few days. Thanks, Tom On Tu

Re: Removing references to Master

thanks for the interest, I haven't had time to work on replacing Master, hopefully for the next release but time dependent, if you follow the lira -  https://issues.apache.org/jira/browse/SPARK-32333 - I will post there when I start or if someone else picks it up should see activity there. Tom

Re: Removing references to Master

So, it looks like slave was already replaced in the docs. Waiting for a definition on the replacement(s) for master so I can create a PR for the docs only. On Sat, Jan 16, 2021 at 8:30 AM jpaulorio wrote: > What about updating the documentation as well? Does it depend on the > codebase > changes

Re: Removing references to Master

What about updating the documentation as well? Does it depend on the codebase changes or can we treat it as a separate issue? I volunteer to update both Master and Slave terms when there's an agreement on what should be used as replacement. Since [SPARK-32004]

Re: Removing references to Master

Thanks for the replies so far, is there any other feedback here?    Of the replies so far I think Leader has been mentioned the most. Tom On Tuesday, August 4, 2020, 09:33:14 AM CDT, Russell Spitzer wrote: I think we should use Scheduler or Comptroller or Leader; something that evokes

Re: Removing references to Master

I think we should use Scheduler or Comptroller or Leader; something that evokes better describes the purpose as a resource management service. I would rather we didn't use controller, coordinator, application manager, primary because I feel that those terms make it seem like the process is central

Re: Removing references to Master

I think this is a good idea, and yes keeping it backwards compatible initially is important since we missed the boat on Spark 3. I like the Controller/Leader one since I think that does a good job of reflecting the codes role. On Tue, Aug 4, 2020 at 7:01 AM Tom Graves wrote: > Hey everyone, > >

Removing references to Master

Hey everyone, I filed jira https://issues.apache.org/jira/browse/SPARK-32333 to remove references to Master.  I realize this is a bigger change then the slave jira but I wanted to get folks input on if they are ok with making the change and if so we would need to pick a name to use instead.  I t