[ https://issues.apache.org/jira/browse/SPARK-32333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405904#comment-17405904 ]
Erik Krogen commented on SPARK-32333: ------------------------------------- Personally, tackling publicly-facing things is my highest priority. This blocks other projects/users from being able to pursue their own efforts in this area. For example, internally we have code with references to the {{--master}} argument, and can't drop these references because of lack of an alternative. So this would be (1) above, though I'll note that things like {{SparkConf.setMaster}} are used beyond the context of standalone mode. For (2) / (3), I'm actually kind of surprised to see there's not _too_ many: {code} . find . -name "*.scala" -or -name "*.java" | xargs grep -o -i -E "class [[:alpha:][:digit:]]*master[[:alpha:][:digit:]]*" ./resource-managers/yarn/src/test/scala/org/apache/spark/deploy/yarn/ApplicationMasterSuite.scala:class ApplicationMasterSuite ./resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMasterArguments.scala:class ApplicationMasterArguments ./resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala:class ApplicationMaster ./resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMasterSource.scala:class ApplicationMasterSource ./core/src/test/scala/org/apache/spark/deploy/master/ui/MasterWebUISuite.scala:class MasterWebUISuite ./core/src/test/scala/org/apache/spark/deploy/master/MasterSuite.scala:class MasterSuite ./core/src/test/scala/org/apache/spark/deploy/rest/StandaloneRestSubmitSuite.scala:class DummyMaster ./core/src/test/scala/org/apache/spark/deploy/rest/StandaloneRestSubmitSuite.scala:class SmarterMaster ./core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala:class MyBlockManagerMaster ./core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala:class MyMapOutputTrackerMaster ./core/src/test/scala/org/apache/spark/storage/BlockManagerMasterSuite.scala:class BlockManagerMasterSuite ./core/src/main/scala/org/apache/spark/deploy/DeployMessage.scala:class MasterChangeAcknowledged ./core/src/main/scala/org/apache/spark/deploy/DeployMessage.scala:class MasterChanged ./core/src/main/scala/org/apache/spark/deploy/DeployMessage.scala:class MasterStateResponse ./core/src/main/scala/org/apache/spark/deploy/FaultToleranceTest.scala:class TestMasterInfo ./core/src/main/scala/org/apache/spark/deploy/master/ui/MasterPage.scala:class MasterPage ./core/src/main/scala/org/apache/spark/deploy/master/ui/MasterWebUI.scala:class MasterWebUI ./core/src/main/scala/org/apache/spark/deploy/master/MasterArguments.scala:class MasterArguments ./core/src/main/scala/org/apache/spark/deploy/master/Master.scala:class Master ./core/src/main/scala/org/apache/spark/deploy/master/MasterSource.scala:class MasterSource ./core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala:class BlockManagerMaster ./core/src/main/scala/org/apache/spark/storage/BlockManagerMasterHeartbeatEndpoint.scala:class BlockManagerMasterHeartbeatEndpoint ./core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala:class BlockManagerMasterEndpoint ./core/src/main/scala/org/apache/spark/MapOutputTracker.scala:class MapOutputTrackerMasterEndpoint ./core/src/main/scala/org/apache/spark/MapOutputTracker.scala:class MapOutputTrackerMaster {code} So it seems that it's likely reasonable to tackle given the breakdown you've outlined. Though the entire {{org.apache.spark.deploy.master}} package will also have to be renamed as part of (2). > 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