Why don't you call them "directors" and "workers" instead of
"masters" and "slaves" ?

Mark

For MapReduce, I always call them "JobTracker" and "TaskTracker", for HDFS,
"Namenode" and "DataNode"

because of the name of classes in source code???:-)

Nan

On Mon, Jun 13, 2011 at 8:25 AM, Mark Hedges <[EMAIL PROTECTED]> wrote:

>
> Why don't you call them "directors" and "workers" instead of
> "masters" and "slaves" ?
>
> Mark
>
>
--
Nan Zhu
School of Electronic, Information and Electrical Engineering,229
Shanghai Jiao Tong University
800,Dongchuan Road,Shanghai,China
E-Mail: [EMAIL PROTECTED]

It is a common term, just one that I have seen distastefully
used with an unpleasant subtext.  Just reading the manual...
Hadoop is neat-o!  --mark--
On Mon, 13 Jun 2011, Nan Zhu wrote:

> For MapReduce, I always call them "JobTracker" and
> "TaskTracker", for HDFS, "Namenode" and "DataNode"
>
> because of the name of classes in source code???:-)
>
> On Mon, Jun 13, 2011 at 8:25 AM, Mark Hedges <[EMAIL PROTECTED]> wrote:
>
> > Why don't you call them "directors" and "workers"
> > instead of "masters" and "slaves" ?

Master and slaves comes from the old distributed system terminologies .
Since Hadoop also is a distributed system it uses that type of terminology
:)

On Mon, Jun 13, 2011 at 6:36 AM, Mark Hedges <[EMAIL PROTECTED]> wrote:

>
> It is a common term, just one that I have seen distastefully
> used with an unpleasant subtext.  Just reading the manual...
> Hadoop is neat-o!  --mark--
>
>
> On Mon, 13 Jun 2011, Nan Zhu wrote:
>
> > For MapReduce, I always call them "JobTracker" and
> > "TaskTracker", for HDFS, "Namenode" and "DataNode"
> >
> > because of the name of classes in source code???:-)
> >
> > On Mon, Jun 13, 2011 at 8:25 AM, Mark Hedges <[EMAIL PROTECTED]>
> wrote:
> >
> > > Why don't you call them "directors" and "workers"
> > > instead of "masters" and "slaves" ?
>