I'm not really for or against changing the name, but I am against the leader/follower suggestions. To me, leader/follower is more of a high availability construct. e.g. running multiple Mesos master processes, just in case one dies. One master would be the leader and the others the follower until a new leader is needed like Zookeeper.
Also, this seems to be a hot topic, and I did see the Apache rules posted in another thread here, but please refrain from personal attacks as they aren't constructive (sun-baked Californians, etc) On Thu, Jun 4, 2015 at 9:23 AM, Aaron Carey <[email protected]> wrote: > Thanks James, > > Interesting background! > ________________________________________ > From: CCAAT [[email protected]] > Sent: 04 June 2015 14:05 > To: [email protected] > Cc: [email protected] > Subject: Re: [DISCUSS] Renaming Mesos Slave > > On 06/04/2015 02:32 AM, Aaron Carey wrote: > > +1 to Itamar. > > > > I'd be interested to hear any case studies of how this has been handled > > in other OS projects with master/slave namings if anyone can give > examples? > > Sure it's easy to reasearch, just use 'master-slave' in your search > strings. Here is a good place to start: > > http://en.wikipedia.org/wiki/Master/slave_(technology) > > > hth, > James > > > > > > ------------------------------------------------------------------------ > > *From:* Itamar Ostricher [[email protected]] > > *Sent:* 04 June 2015 05:38 > > *To:* [email protected] > > *Cc:* dev > > *Subject:* Re: [DISCUSS] Renaming Mesos Slave > > > > Strong -1 for changing the name (either master or slave). > > > > From a community stand point, if dev resources are diverted to renaming > > efforts, then the community and the user base both lose meaningful > > functionality that isn't being worked on. > > > > From a using organization stand point, as well as framework developer > > perspective, I follow mesos releases pretty closely, and I'm confident > > that the version that deprecates backward compatibility with the current > > names will be a version I will not be able to adopt for months, if at > all... > > > > So please don't do that, or if you do, consider leaving in a > > configuration option to keep the current names for sane upgrades. > >
