I've created SPARK-32036 <https://issues.apache.org/jira/browse/SPARK-32036> and SPARK-32037 <https://issues.apache.org/jira/browse/SPARK-32037> for changes related to "blacklist"/"whitelist" terminology, the latter of which focuses on the blacklisting feature. I invite all of you to participate in the relevant discussion on SPARK-32037 in particular, given that it would be a substantial rename.
On Fri, Jun 19, 2020 at 1:29 PM Ryan Blue <rb...@netflix.com.invalid> wrote: > Thanks for getting this started! I think it will be worth the effort, and > it's great to get started early in the 3.x release line to give the most > time to prepare for this. > > On Thu, Jun 18, 2020 at 3:44 PM Russell Spitzer <russell.spit...@gmail.com> > wrote: > >> I really dislike the use of "worker" in the code base since it describes >> a process which doesn't actually do work, but I don't think it's in the >> scope for this ticket. I would definitely prefer we use "agent" instead of >> "worker" (or some other name) and have master switched to something like >> "resource manager" or something that actually describes the purpose of the >> process. >> >> I realize that touching "master" is going to disrupt just about >> everything but these name choices are usually the first thing that trips up >> new Spark Users. In my experience, I usually have to spend at least 15-20 >> minutes explaining that a worker will not actually do work, and the master >> won't run their application. >> >> Thanks Holden for doing all the legwork on this! >> > > > -- > Ryan Blue > Software Engineer > Netflix >
