mahout-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <>
Subject Re: Plans For Migrating Drivers to Tool interface?
Date Wed, 28 Oct 2009 09:48:01 GMT
That looks a lot like an arg that sets a system property in the JVM.
And it sounds like you're passing it to the Java program rather than
Java. Just put it before the class name? that is... "java -D...
org.apache... foo bar baz"

On Wed, Oct 28, 2009 at 1:10 AM, Gregory Lawrence <> wrote:
> Hi,
> I'm having trouble running the KMeansDriver and I suspect that the problem is related
to Adil's message. I'm in an environment which recently switched to Hadoop 0.2. I am no longer
able to use hod as a scheduler. Furthermore, I'm forced to specify the queue (which unfortunately
is not named default). This is normally done using Is there any way
that I will be able to use Mahout, specifically the clustering code? When I run the KmeansDriver
code with the -D option, it gives the following error message:
> 09/10/28 01:09:21 ERROR kmeans.KMeansDriver: Exception
> org.apache.commons.cli2.OptionException: Unexpected -D while processing Options
> On 9/14/09 3:19 PM, "Adil Aijaz" <> wrote:
> Hi folks,
> I just recently merged my vendor branch of Mahout with Mahout trunk and
> found that Mahout now supports Hadoop 0.20. Now, with Hadoop 0.20, we
> now have the ability to use capacity scheduler instead of hod. There are
> two ways to pass on the capacity scheduler queue name to a Mahout driver
> class like KMeansDriver:
> 1. Have KMeansDriver extend 'Configured' and implement 'Tool' interface
> to allow command line specification of the scheduler queue name as in
> 2. Add jobConfi.set() while setting up the drivers.
> Personally, I prefer the first solution. Are there any plans on updating
> the various driver classes to support such capacity scheduler queues?
> Either way, I can help out in the process.
> Adil

View raw message