mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Spitz <>
Subject Re: Getting mahout to run on the DFS
Date Mon, 01 Nov 2010 20:40:48 GMT
Gah, that's ridiculous.  I didn't specify MAHOUT_HOME, which makes our

So, running locally (no HADOOP_HOME/HADOOP_CONF_DIR set), kmeans runs fine
with -xm mapreduce and -xm sequential.

Running on hadoop (using HADOOP_HOME/HADOOP_CONF_DIR), kmeans runs fine with
-xm sequential, but runs into the exception mentioned above with -xm

There's gotta be something different about the way in which we browse our
filesystems on the DFS.  Or perhaps the permissions with which these things
are created?

Looks like the clusters/part-randomSeed is -rw-r--r--, which is the same as
all of the chunk-* files in reuters-out-seqdir.

I'm stumped.


On Mon, Nov 1, 2010 at 12:26 PM, Jeff Eastman <> wrote:

> Frustrating. We're both running CHD3, right? That's Hadoop 0.20.2. I added
> the echos you suggested and my Classpath: output is empty. My Command:
> output is essentially the same as what you reported.
> -----Original Message-----
> From: Matt Spitz []
> Sent: Monday, November 01, 2010 8:59 AM
> To:
> Subject: Re: Getting mahout to run on the DFS
> Blast!  I ran it as another user, and no dice.  Same error.
> I guess my question for you was to figure out what your classpath was and
> see if there was anything different.  bin/mahout is just a simple script,
> and I was just adding a quick 'echo' to it.
> What version of hadoop are you running?  I wonder if the "Path" class is
> defined differently for different versions.
> Thanks,
> Matt
> On Sat, Oct 30, 2010 at 4:56 PM, Jeff Eastman <
> >wrote:
> > On 10/29/10 10:09 AM, Jeff Eastman wrote:
> >
> >> Ok, very interesting. I think you are onto the root cause. I can't work
> on
> >> this until the weekend but will investigate further then.
> >>
> >>  I tried creating another user on my CHD3 box and, for a minute, thought
> I
> > could duplicate something like your problem. But it was a permission
> problem
> > in examples/bin/work that resulted in 0 vectors being output from
> > seq2sparse. That caused an array indexing error in RandomSeed generator
> but
> > it went away when I made /work be 777. Even in that situation, I got the
> > same error (of course) running kmeans -xm sequential.
> >
> > You can modify bin/mahout to your heart's content. I hope you are having
> > better luck than I am. Build-reuters works perfectly under both userIds.
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message