What is your 'classic' MapReduce bundle version? 0.23 ships no classic
MapReduce services bundle in it AFAIK, only YARN+(MR2-App).

Whatever version you're trying to use, make sure it is not using the
older HDFS jars?

On Wed, Oct 3, 2012 at 10:13 AM, Alexander Hristov <alexh@planetalia.com> wrote:
> Hi again
>
> Why does it seem to me that everything Hadoop 0.23-related is an uphill
> battle? :-(
>
> I'm trying something as simple as running a classic(MapReduce 1) Hadoop
> cluster. Here's my configuration:
>
> core-site.xml:
> <configuration>
>     <property>
>       <name>fs.default.name</name>
>       <value>hdfs://samplehost.com:9000</value>
>     </property>
> </configuration>
>
> hdfs-site.xml
> <configuration>
>      <property>
>          <name>dfs.replication</name>
>          <value>3</value>
>      </property>
> </configuration>
>
> mapred-site.xml
> <configuration>
>   <property>
>     <name>mapreduce.framework.name</name>
>     <value>classic</value>
>   </property>
>   <property>
>     <name>mapred.job.tracker</name>
>     <value>samplehost.com:9001</value>
>   </property>
>     <property>
>     <name> mapreduce.jobtracker.address</name>
>     <value>samplehost.com:9001</value>
>   </property>
> </configuration>
>
> yarn-site.xml
> <configuration>
> </configuration>
>
>
> Well, I start the thing and do a netstat -l , and there's no one listening
> on port 9001. There are no errors in the logs, and no mention of that port,
> either.
> Obviously, all Map/Reduce examples fail with Connection Refused.
>
> Starting the same cluster using a MapReduce 2 (YARN) configuration works
> properly.
>
> Regards,
>
> Alexander
>
>
>



-- 
Harsh J