[ https://issues.apache.org/jira/browse/SPARK-32333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378093#comment-17378093 ]
Thomas Graves commented on SPARK-32333: --------------------------------------- Getting back to this, now that spark 3.2 branch is cut, perhaps we can target for 3.3. >From the discussion thread on spark-dev mailing list Leader was mentioned the >most, Scheduler a second. One reason against controller, coordinator, application manager, primary as it perhaps implies being needed and if the standalone master goes down the apps are unaffected. Based on the feedback, I propose "Leader" based on feedback and it being short. > Drop references to Master > ------------------------- > > Key: SPARK-32333 > URL: https://issues.apache.org/jira/browse/SPARK-32333 > Project: Spark > Issue Type: Improvement > Components: Spark Core, SQL > Affects Versions: 3.0.0 > Reporter: Thomas Graves > Priority: Major > > We have a lot of references to "master" in the code base. It will be > beneficial to remove references to problematic language that can alienate > potential community members. > SPARK-32004 removed references to slave > > Here is a IETF draft to fix up some of the most egregious examples > (master/slave, whitelist/backlist) with proposed alternatives. > https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org