You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Peter Goldstein (JIRA)" <ji...@apache.org> on 2010/06/23 07:32:51 UTC
[jira] Created: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
-------------------------------------------------------------------------------------------------------------------
Key: MAHOUT-428
URL: https://issues.apache.org/jira/browse/MAHOUT-428
Project: Mahout
Issue Type: Bug
Components: Clustering
Affects Versions: 0.4
Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
Reporter: Peter Goldstein
Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885595#action_12885595 ]
Ted Dunning commented on MAHOUT-428:
------------------------------------
THis looks non-controversial and safe.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885544#action_12885544 ]
Drew Farris commented on MAHOUT-428:
------------------------------------
IIRC, this doesn't show up when running locally but does come up when running on a hadoop cluster. Can't verify at the moment however.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Dunning resolved MAHOUT-428.
--------------------------------
Resolution: Fixed
Applied Peter's patch.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Assignee: Ted Dunning
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Peter Goldstein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885578#action_12885578 ]
Peter Goldstein commented on MAHOUT-428:
----------------------------------------
I ran into this issue when deploying on a Hadoop install on an EC2 machine, following the EC2 deployment instructions on the wiki. I ran through the steps (starting from a clean server) multiple times, and I reproduced this issue each time.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885534#action_12885534 ]
Grant Ingersoll commented on MAHOUT-428:
----------------------------------------
It works for me w/o the modification. What steps did you do to reproduce this?
I'm guessing it works for me b/c I did a mvn install first.
At any rate, the patch seems fine, too, just curious why I'm not seeing it.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885609#action_12885609 ]
Hudson commented on MAHOUT-428:
-------------------------------
Integrated in Mahout-Quality #120 (See [http://hudson.zones.apache.org/hudson/job/Mahout-Quality/120/])
MAHOUT-428 Applied Peter's patch
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Assignee: Ted Dunning
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Peter Goldstein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Goldstein updated MAHOUT-428:
-----------------------------------
Attachment: MAHOUT-428.patch
This patch adds a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java code, ensuring that the job classpath is set up correctly.
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAHOUT-428) KMeansDriver: No job jar file set
leads to ClassNotFoundException:
org.apache.mahout.clustering.kmeans.KMeansMapper
Posted by "Ted Dunning (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Dunning reassigned MAHOUT-428:
----------------------------------
Assignee: Ted Dunning
> KMeansDriver: No job jar file set leads to ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAHOUT-428
> URL: https://issues.apache.org/jira/browse/MAHOUT-428
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.4
> Environment: ubuntu 8.10, sun jdk 1.6.0_10-b33, hadoop cluster running 0.20.2+228, build from r957113 of http://svn.apache.org/repos/asf/lucene/mahout/trunk
> Reporter: Peter Goldstein
> Assignee: Ted Dunning
> Attachments: MAHOUT-428.patch
>
>
> Running the $MAHOUT_HOME/examples/bin/build-reuters.sh script I encountered the following exception:
> 10/06/23 04:41:00 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String).
> 10/06/23 04:41:01 INFO input.FileInputFormat: Total input paths to process : 1
> 10/06/23 04:41:01 INFO mapred.JobClient: Running job: job_201006222301_0019
> 10/06/23 04:41:02 INFO mapred.JobClient: map 0% reduce 0%
> 10/06/23 04:41:11 INFO mapred.JobClient: Task Id : attempt_201006222301_0019_m_000000_0, Status : FAILED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.mahout.clustering.kmeans.KMeansMapper
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:960)
> at org.apache.hadoop.mapreduce.JobContext.getMapperClass(JobContext.java:158)
> This appears to be identical in cause to MAHOUT-197 , and has an almost identical fix. Adding a job.setJarByClass(KMeansDriver.class) line to the KMeansDriver.java file fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.