Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - NoSuchColumnFamilyException with rowcounter


Copy link to this message
-
Re: NoSuchColumnFamilyException with rowcounter
Jean-Marc Spaggiari 2012-10-11, 17:43
:(

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
>