Hi,

When I'm trying to run RowCounter, I'm getting the error below.,

12/10/11 13:09:58 INFO mapred.JobClient: Task Id :
attempt_201209151131_0022_m_000013_0, Status : FAILED
org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
Column family -D does not exist in region
work_proposed,\x82,1342541226467.a58d532e688cbb185beb40d301be768e. in
table {NAME => 'work_proposed', FAMILIES => [{NAME => '@',
DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'NONE',
REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '3', TTL
=> '2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false',
BLOCKSIZE => '65536', ENCODE_ON_DISK => 'true', IN_MEMORY => 'false',
BLOCKCACHE => 'true'}]}

In this table, I have only one familly called #64 (@) and one column
called #64 (@). I'm not using the content. Only the keys.

Files seems to be fine:
Number of empty REGIONINFO_QUALIFIER rows in .META.: 0
12/10/11 13:24:05 DEBUG util.HBaseFsck: There are 138 region info entries
Summary:
  -ROOT- is okay.
    Number of regions: 1
    Deployed on:  node1,60020,1349286129520
  .META. is okay.
    Number of regions: 1
    Deployed on:  node3,60020,1349286137152

.
.
.

  work_proposed is okay.
    Number of regions: 25
    Deployed on:  latitude,60020,1349734460663
node1,60020,1349286129520 node3,60020,1349286137152
node4,60020,1349962953166 node5,60020,1349960301032
phenom,60020,1349955670902
  work_sent is okay.
    Number of regions: 25
    Deployed on:  latitude,60020,1349734460663
node1,60020,1349286129520 node3,60020,1349286137152
node4,60020,1349962953166 node5,60020,1349960301032
phenom,60020,1349955670902
0 inconsistencies detected.
Status: OK

And I'm running the command line with that:
export HADOOP_HOME=/home/hadoop/hadoop-1.0.3/; export
HBASE_HOME=/home/hbase/hbase-0.94.0/;
HADOOP_CLASSPATH=`${HBASE_HOME}/bin/hbase classpath`
${HADOOP_HOME}/bin/hadoop jar ${HBASE_HOME}/hbase-0.94.1.jar
rowcounter work_proposed -Dhbase.client.scanner.caching=10
Any idea where I can dig to understand why it's looking for a column
familly which doesn't exist?

JM

Jean-Marc,

  If you remove your -D flag does you command run successfully?  I always
forget there this goes as well, but It should be one of the two:

${HADOOP_HOME}/bin/hadoop jar
${HBASE_HOME}/hbase-0.94.1.jar -Dhbase.client.scanner.caching=10 rowcounter
work_proposed

${HADOOP_HOME}/bin/hadoop jar
${HBASE_HOME}/hbase-0.94.1.jar rowcounter
-Dhbase.client.scanner.caching=10 work_proposed

On Thu, Oct 11, 2012 at 1:26 PM, Jean-Marc Spaggiari <
[EMAIL PROTECTED]> wrote:

> Hi,
>
> When I'm trying to run RowCounter, I'm getting the error below.,
>
> 12/10/11 13:09:58 INFO mapred.JobClient: Task Id :
> attempt_201209151131_0022_m_000013_0, Status : FAILED
> org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
> org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
> Column family -D does not exist in region
> work_proposed,\x82,1342541226467.a58d532e688cbb185beb40d301be768e. in
> table {NAME => 'work_proposed', FAMILIES => [{NAME => '@',
> DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'NONE',
> REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '3', TTL
> => '2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false',
> BLOCKSIZE => '65536', ENCODE_ON_DISK => 'true', IN_MEMORY => 'false',
> BLOCKCACHE => 'true'}]}
>
> In this table, I have only one familly called #64 (@) and one column
> called #64 (@). I'm not using the content. Only the keys.
>
> Files seems to be fine:
> Number of empty REGIONINFO_QUALIFIER rows in .META.: 0
> 12/10/11 13:24:05 DEBUG util.HBaseFsck: There are 138 region info entries
> Summary:
>   -ROOT- is okay.
>     Number of regions: 1
>     Deployed on:  node1,60020,1349286129520
>   .META. is okay.
>     Number of regions: 1
>     Deployed on:  node3,60020,1349286137152
>
> .
> .
> .
>
>   work_proposed is okay.
>     Number of regions: 25
>     Deployed on:  latitude,60020,1349734460663
> node1,60020,1349286129520 node3,60020,1349286137152
> node4,60020,1349962953166 node5,60020,1349960301032
> phenom,60020,1349955670902
>   work_sent is okay.
>     Number of regions: 25
>     Deployed on:  latitude,60020,1349734460663
> node1,60020,1349286129520 node3,60020,1349286137152
> node4,60020,1349962953166 node5,60020,1349960301032
> phenom,60020,1349955670902
> 0 inconsistencies detected.
> Status: OK
>
> And I'm running the command line with that:
> export HADOOP_HOME=/home/hadoop/hadoop-1.0.3/; export
> HBASE_HOME=/home/hbase/hbase-0.94.0/;
> HADOOP_CLASSPATH=`${HBASE_HOME}/bin/hbase classpath`
> ${HADOOP_HOME}/bin/hadoop jar ${HBASE_HOME}/hbase-0.94.1.jar
> rowcounter work_proposed -Dhbase.client.scanner.caching=10
>
>
> Any idea where I can dig to understand why it's looking for a column
> familly which doesn't exist?
>
> JM
>

--
Kevin O'Dell
Customer Operations Engineer, Cloudera

:(

That's where the "-D" column name is coming!!!! :(

I tried to move it to few places before and it was not working. That's
the only place where it's not crashing right from the launch.

If you place it after the "rowcounter", it takes it as the table name.
If you place it before, it takes it as the job name ;)

I will do some retries to see if I can find a proper place.

Thanks again,

JM

2012/10/11, Kevin O'dell <[EMAIL PROTECTED]>:
> Jean-Marc,
>
>   If you remove your -D flag does you command run successfully?  I always
> forget there this goes as well, but It should be one of the two:
>
> ${HADOOP_HOME}/bin/hadoop jar
> ${HBASE_HOME}/hbase-0.94.1.jar -Dhbase.client.scanner.caching=10 rowcounter
> work_proposed
>
> ${HADOOP_HOME}/bin/hadoop jar
> ${HBASE_HOME}/hbase-0.94.1.jar rowcounter
> -Dhbase.client.scanner.caching=10 work_proposed
>
> On Thu, Oct 11, 2012 at 1:26 PM, Jean-Marc Spaggiari <
> [EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> When I'm trying to run RowCounter, I'm getting the error below.,
>>
>> 12/10/11 13:09:58 INFO mapred.JobClient: Task Id :
>> attempt_201209151131_0022_m_000013_0, Status : FAILED
>> org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
>> org.apache.hadoop.hbase.regionserver.NoSuchColumnFamilyException:
>> Column family -D does not exist in region
>> work_proposed,\x82,1342541226467.a58d532e688cbb185beb40d301be768e. in
>> table {NAME => 'work_proposed', FAMILIES => [{NAME => '@',
>> DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'NONE',
>> REPLICATION_SCOPE => '0', COMPRESSION => 'NONE', VERSIONS => '3', TTL
>> => '2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false',
>> BLOCKSIZE => '65536', ENCODE_ON_DISK => 'true', IN_MEMORY => 'false',
>> BLOCKCACHE => 'true'}]}
>>
>> In this table, I have only one familly called #64 (@) and one column
>> called #64 (@). I'm not using the content. Only the keys.
>>
>> Files seems to be fine:
>> Number of empty REGIONINFO_QUALIFIER rows in .META.: 0
>> 12/10/11 13:24:05 DEBUG util.HBaseFsck: There are 138 region info entries
>> Summary:
>>   -ROOT- is okay.
>>     Number of regions: 1
>>     Deployed on:  node1,60020,1349286129520
>>   .META. is okay.
>>     Number of regions: 1
>>     Deployed on:  node3,60020,1349286137152
>>
>> .
>> .
>> .
>>
>>   work_proposed is okay.
>>     Number of regions: 25
>>     Deployed on:  latitude,60020,1349734460663
>> node1,60020,1349286129520 node3,60020,1349286137152
>> node4,60020,1349962953166 node5,60020,1349960301032
>> phenom,60020,1349955670902
>>   work_sent is okay.
>>     Number of regions: 25
>>     Deployed on:  latitude,60020,1349734460663
>> node1,60020,1349286129520 node3,60020,1349286137152
>> node4,60020,1349962953166 node5,60020,1349960301032
>> phenom,60020,1349955670902
>> 0 inconsistencies detected.
>> Status: OK
>>
>> And I'm running the command line with that:
>> export HADOOP_HOME=/home/hadoop/hadoop-1.0.3/; export
>> HBASE_HOME=/home/hbase/hbase-0.94.0/;
>> HADOOP_CLASSPATH=`${HBASE_HOME}/bin/hbase classpath`
>> ${HADOOP_HOME}/bin/hadoop jar ${HBASE_HOME}/hbase-0.94.1.jar
>> rowcounter work_proposed -Dhbase.client.scanner.caching=10
>>
>>
>> Any idea where I can dig to understand why it's looking for a column
>> familly which doesn't exist?
>>
>> JM
>>
>
>
>
> --
> Kevin O'Dell
> Customer Operations Engineer, Cloudera
>

On Thu, Oct 11, 2012 at 10:43 AM, Jean-Marc Spaggiari
<[EMAIL PROTECTED]> wrote:
> :(
>
> That's where the "-D" column name is coming!!!! :(
>
> I tried to move it to few places before and it was not working. That's
> the only place where it's not crashing right from the launch.
>
> If you place it after the "rowcounter", it takes it as the table name.
> If you place it before, it takes it as the job name ;)
>
> I will do some retries to see if I can find a proper place.
>

It doesn't work before the table name?  Let us know J-M so we can
update "14.1.12. RowCounter" in the book.
St.Ack

On Thu, Oct 11, 2012 at 1:09 PM, Stack <[EMAIL PROTECTED]> wrote:
> It doesn't work before the table name?  Let us know J-M so we can
> update "14.1.12. RowCounter" in the book.

FWIW I did a test locally and it worked. That's also how I expect
GenericOptionsParser to behave.

J-D

No, the line in the book is correct. I was trying to use another one
command line (See in the first post). I think it was not working
because of some _HOME issues which are deprecated.

I'm now using thsi command line and it's working fine (except for the
number of tasks).
HADOOP_CLASSPATH=`/home/hbase/hbase-0.94.0/bin/hbase
classpath`:`/home/hadoop/hadoop-1.0.3/bin/hadoop classpath`
/home/hadoop/hadoop-1.0.3/bin/hadoop jar
/home/hbase/hbase-0.94.0/hbase-0.94.1.jar rowcounter
-Dhbase.client.scanner.caching=100 -Dmapred.map.tasks=6
-Dmapred.map.tasks.speculative.execution=false work_proposed

I simply don't know if the -D parameters are taken into consideration
since I get the same results (numbers of tasks, time of exec, etc.)
with and without them.

JM

2012/10/11, Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> On Thu, Oct 11, 2012 at 1:09 PM, Stack <[EMAIL PROTECTED]> wrote:
>> It doesn't work before the table name?  Let us know J-M so we can
>> update "14.1.12. RowCounter" in the book.
>
> FWIW I did a test locally and it worked. That's also how I expect
> GenericOptionsParser to behave.
>
> J-D
>

On Thu, Oct 11, 2012 at 1:20 PM, Jean-Marc Spaggiari
<[EMAIL PROTECTED]> wrote:
> I'm now using thsi command line and it's working fine (except for the
> number of tasks).
> HADOOP_CLASSPATH=`/home/hbase/hbase-0.94.0/bin/hbase
> classpath`:`/home/hadoop/hadoop-1.0.3/bin/hadoop classpath`
> /home/hadoop/hadoop-1.0.3/bin/hadoop jar
> /home/hbase/hbase-0.94.0/hbase-0.94.1.jar rowcounter
> -Dhbase.client.scanner.caching=100 -Dmapred.map.tasks=6
> -Dmapred.map.tasks.speculative.execution=false work_proposed
>
> I simply don't know if the -D parameters are taken into consideration
> since I get the same results (numbers of tasks, time of exec, etc.)
> with and without them.

Using a higher caching value won't do much good if you don't have a
lot of rows. Since you didn't include any data like that in your
email, I won't guess how much 100 would help your case.

The number of map tasks when mapping an HBase table will be the number
of regions you have in that table. Unfortunately you can't change it
unless you write your own input format for HBase.

J-D

Hi J-D,

I have about 20M rows over 25 regions on 6 nodes. So that mean I
should see something like 6 tasks or even 25, right? And not just 2?
Keys are 128 byte long. Value is 1 byte.

I tried also to update mapreduce.tasktracker.map.tasks.maximum but
this is "the number of map tasks that should be launched on each node,
not the number of nodes to be used for each map task.", so there was
no changes, as expected.

JM

2012/10/11 Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> On Thu, Oct 11, 2012 at 1:20 PM, Jean-Marc Spaggiari
> <[EMAIL PROTECTED]> wrote:
>> I'm now using thsi command line and it's working fine (except for the
>> number of tasks).
>> HADOOP_CLASSPATH=`/home/hbase/hbase-0.94.0/bin/hbase
>> classpath`:`/home/hadoop/hadoop-1.0.3/bin/hadoop classpath`
>> /home/hadoop/hadoop-1.0.3/bin/hadoop jar
>> /home/hbase/hbase-0.94.0/hbase-0.94.1.jar rowcounter
>> -Dhbase.client.scanner.caching=100 -Dmapred.map.tasks=6
>> -Dmapred.map.tasks.speculative.execution=false work_proposed
>>
>> I simply don't know if the -D parameters are taken into consideration
>> since I get the same results (numbers of tasks, time of exec, etc.)
>> with and without them.
>
> Using a higher caching value won't do much good if you don't have a
> lot of rows. Since you didn't include any data like that in your
> email, I won't guess how much 100 would help your case.
>
> The number of map tasks when mapping an HBase table will be the number
> of regions you have in that table. Unfortunately you can't change it
> unless you write your own input format for HBase.
>
> J-D

2 tasks total or that are running at the same time? If latter, it just
means that you are using the local job tracker instead of your job
tracker because HBase couldn't find your MR config.

J-D

On Thu, Oct 11, 2012 at 1:36 PM, Jean-Marc Spaggiari
<[EMAIL PROTECTED]> wrote:
> Hi J-D,
>
> I have about 20M rows over 25 regions on 6 nodes. So that mean I
> should see something like 6 tasks or even 25, right? And not just 2?
> Keys are 128 byte long. Value is 1 byte.
>
> I tried also to update mapreduce.tasktracker.map.tasks.maximum but
> this is "the number of map tasks that should be launched on each node,
> not the number of nodes to be used for each map task.", so there was
> no changes, as expected.
>
> JM
>
> 2012/10/11 Jean-Daniel Cryans <[EMAIL PROTECTED]>:
>> On Thu, Oct 11, 2012 at 1:20 PM, Jean-Marc Spaggiari
>> <[EMAIL PROTECTED]> wrote:
>>> I'm now using thsi command line and it's working fine (except for the
>>> number of tasks).
>>> HADOOP_CLASSPATH=`/home/hbase/hbase-0.94.0/bin/hbase
>>> classpath`:`/home/hadoop/hadoop-1.0.3/bin/hadoop classpath`
>>> /home/hadoop/hadoop-1.0.3/bin/hadoop jar
>>> /home/hbase/hbase-0.94.0/hbase-0.94.1.jar rowcounter
>>> -Dhbase.client.scanner.caching=100 -Dmapred.map.tasks=6
>>> -Dmapred.map.tasks.speculative.execution=false work_proposed
>>>
>>> I simply don't know if the -D parameters are taken into consideration
>>> since I get the same results (numbers of tasks, time of exec, etc.)
>>> with and without them.
>>
>> Using a higher caching value won't do much good if you don't have a
>> lot of rows. Since you didn't include any data like that in your
>> email, I won't guess how much 100 would help your case.
>>
>> The number of map tasks when mapping an HBase table will be the number
>> of regions you have in that table. Unfortunately you can't change it
>> unless you write your own input format for HBase.
>>
>> J-D

2 tasks at the same time, for a total of 25 tasks at the end.

Maybe as you are saying, I'm not facing the good jobtracker? I'm
running the command line on the master server.

If I look at the map tasks, I can see that:
Input Split Locations /default-rack/node1

With differents values depending on the tasks, but on the same page I
can see machine=/default-rack/node3 (which is my master).

How/where should I run this? Should I point it to Zookeeper instance instead?

Thanks,

JM
2012/10/11 Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> 2 tasks total or that are running at the same time? If latter, it just
> means that you are using the local job tracker instead of your job
> tracker because HBase couldn't find your MR config.
>
> J-D
>
> On Thu, Oct 11, 2012 at 1:36 PM, Jean-Marc Spaggiari
> <[EMAIL PROTECTED]> wrote:
>> Hi J-D,
>>
>> I have about 20M rows over 25 regions on 6 nodes. So that mean I
>> should see something like 6 tasks or even 25, right? And not just 2?
>> Keys are 128 byte long. Value is 1 byte.
>>
>> I tried also to update mapreduce.tasktracker.map.tasks.maximum but
>> this is "the number of map tasks that should be launched on each node,
>> not the number of nodes to be used for each map task.", so there was
>> no changes, as expected.
>>
>> JM
>>
>> 2012/10/11 Jean-Daniel Cryans <[EMAIL PROTECTED]>:
>>> On Thu, Oct 11, 2012 at 1:20 PM, Jean-Marc Spaggiari
>>> <[EMAIL PROTECTED]> wrote:
>>>> I'm now using thsi command line and it's working fine (except for the
>>>> number of tasks).
>>>> HADOOP_CLASSPATH=`/home/hbase/hbase-0.94.0/bin/hbase
>>>> classpath`:`/home/hadoop/hadoop-1.0.3/bin/hadoop classpath`
>>>> /home/hadoop/hadoop-1.0.3/bin/hadoop jar
>>>> /home/hbase/hbase-0.94.0/hbase-0.94.1.jar rowcounter
>>>> -Dhbase.client.scanner.caching=100 -Dmapred.map.tasks=6
>>>> -Dmapred.map.tasks.speculative.execution=false work_proposed
>>>>
>>>> I simply don't know if the -D parameters are taken into consideration
>>>> since I get the same results (numbers of tasks, time of exec, etc.)
>>>> with and without them.
>>>
>>> Using a higher caching value won't do much good if you don't have a
>>> lot of rows. Since you didn't include any data like that in your
>>> email, I won't guess how much 100 would help your case.
>>>
>>> The number of map tasks when mapping an HBase table will be the number
>>> of regions you have in that table. Unfortunately you can't change it
>>> unless you write your own input format for HBase.
>>>
>>> J-D

On Thu, Oct 11, 2012 at 1:53 PM, Jean-Marc Spaggiari
<[EMAIL PROTECTED]> wrote:
> 2 tasks at the same time, for a total of 25 tasks at the end.

This really sounds like the local job runner.

>
> Maybe as you are saying, I'm not facing the good jobtracker? I'm
> running the command line on the master server.

What I said is that you haven't configured HBase to know about your
job tracker. The fact that they are on the same machine isn't enough.

Although, you are indeed passing by the bin/hadoop command in the row
counter case... is your job tracker even running? Can we see a full
log of what happens after you start your job? Use pastebin.com or such
please.

J-D

Thanks for your support.

Here is the pastbin: http://pastebin.com/VM41hK9X

And here is the config file:
hadoop@node3:~/hadoop-1.0.3$ cat conf/mapred-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>

<!-- Put site-specific property overrides in this file. -->

<configuration>
     <property>
         <name>mapred.job.tracker</name>
         <value>localhost:9001</value>
     </property>
      <property>
        <name>dfs.datanode.max.xcievers</name>
        <value>4096</value>
      </property>
<property>
  <name>mapreduce.tasktracker.map.tasks.maximum</name>
  <value>6</value>
  <description>The maximum number of map tasks that will be run
  simultaneously by a task tracker.
  </description>
</property>

<property>
  <name>mapreduce.tasktracker.reduce.tasks.maximum</name>
  <value>6</value>
  <description>The maximum number of reduce tasks that will be run
  simultaneously by a task tracker.
  </description>
</property>
</configuration>
JM
2012/10/11, Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> On Thu, Oct 11, 2012 at 1:53 PM, Jean-Marc Spaggiari
> <[EMAIL PROTECTED]> wrote:
>> 2 tasks at the same time, for a total of 25 tasks at the end.
>
> This really sounds like the local job runner.
>
>>
>> Maybe as you are saying, I'm not facing the good jobtracker? I'm
>> running the command line on the master server.
>
> What I said is that you haven't configured HBase to know about your
> job tracker. The fact that they are on the same machine isn't enough.
>
> Although, you are indeed passing by the bin/hadoop command in the row
> counter case... is your job tracker even running? Can we see a full
> log of what happens after you start your job? Use pastebin.com or such
> please.
>
> J-D
>

Ok so you actually have 12M rows. One thing that surprised me in your config is:

>          <name>mapred.job.tracker</name>
>          <value>localhost:9001</value>

Is it the same config on every node? If so, and your master node also
counts as a slave node (region server, datanode, tasktracker), then
you probably only really have 1 TT running and the others are looking
for their job tracker since it's define as "localhost" and aren't able
to find it.

Please confirm/fix this if needed.

J-D

Ok. I see.

I have that on all the nodes:
<configuration>
     <property>
         <name>mapred.job.tracker</name>
         <value>localhost:9001</value>
     </property>
      <property>
        <name>dfs.datanode.max.xcievers</name>
        <value>4096</value>
      </property>
</configuration>
And that on my master:
hadoop@node3:~$ /usr/local/jdk1.7.0_05/bin/jps
2219 NameNode
2630 Jps
30362 JobTracker
2652 DataNode
30273 TaskTracker
2392 SecondaryNameNode

I will update all the mapred-site.xml and re-start the cluster.

I will keep you posted shortly.

Thanks!

JM

2012/10/11, Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> Ok so you actually have 12M rows. One thing that surprised me in your config
> is:
>
>>          <name>mapred.job.tracker</name>
>>          <value>localhost:9001</value>
>
> Is it the same config on every node? If so, and your master node also
> counts as a slave node (region server, datanode, tasktracker), then
> you probably only really have 1 TT running and the others are looking
> for their job tracker since it's define as "localhost" and aren't able
> to find it.
>
> Please confirm/fix this if needed.
>
> J-D
>

On Thu, Oct 11, 2012 at 2:46 PM, Jean-Marc Spaggiari
<[EMAIL PROTECTED]> wrote:
> And that on my master:
> hadoop@node3:~$ /usr/local/jdk1.7.0_05/bin/jps
> 2219 NameNode
> 2630 Jps
> 30362 JobTracker
> 2652 DataNode
> 30273 TaskTracker
> 2392 SecondaryNameNode

Ah it's like I thought.

>
> I will update all the mapred-site.xml and re-start the cluster.

No need to restart, just do a bin/hadoop-daemons.sh start tasktracker

They should all be dead anyways.

J-D

I saw you message a bit to late ;) I have connected to all the nodes
one by one to restart the deamon.

Now I can see that I have 6 nodes in the Hadoop Map/Reduce
Administration page! I had one in the past, the master. I thought it
was normal.

After restarting I had 10 nodes. So I have also restarted the
jobtracker and now everything seems to be working fine.

Thanks for all your help. I was initially really not looking into the
right direction.

RowCounter is now way faster than the regular "count" from the shell,
which is taking 22 minutes. (6 minutes for the MR).

I will try to see if there is ways to get that even faster...

JM

2012/10/11, Jean-Daniel Cryans <[EMAIL PROTECTED]>:
> On Thu, Oct 11, 2012 at 2:46 PM, Jean-Marc Spaggiari
> <[EMAIL PROTECTED]> wrote:
>> And that on my master:
>> hadoop@node3:~$ /usr/local/jdk1.7.0_05/bin/jps
>> 2219 NameNode
>> 2630 Jps
>> 30362 JobTracker
>> 2652 DataNode
>> 30273 TaskTracker
>> 2392 SecondaryNameNode
>
> Ah it's like I thought.
>
>>
>> I will update all the mapred-site.xml and re-start the cluster.
>
> No need to restart, just do a bin/hadoop-daemons.sh start tasktracker
>
> They should all be dead anyways.
>
> J-D
>