incubator-chukwa-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Yang <>
Subject Re: A demo setup on a single linux server
Date Wed, 01 Jun 2011 18:10:29 GMT
Hi Preetam,

Have you run hbase shell < hbase.schema ?  The problem description has two possible outcomes.

1, Hbase schema has not been applied to hbase. Solution:

Hbase shell < /path/to/chukwa/conf/hbase.schema

2, hbase-site.xml and hadoop-site.xml are not in chukwa configuration directory or nor in
the chukwa collector class path.  Solution:

cp hadoop-site.xml hbase-site.xml /path/to/chukwa/conf

Hope this helps.


On 6/1/11 10:03 AM, "Preetam Patil" <> wrote:

Hi Eric and DKN,

I am facing a similar (maybe a noob) problem: chukwa collector is able
to write to a sequence file, but when I enabl eHBaseWriter, the
HBaseTable entries are not added. I am not sure whether it's a problem
with my HBase setup (it's in standalone mode) or Chukwa Demux parsers.
I get two errors: "ERROR main HBaseWriter - Hbase schema mismatch with
demux parser" and "INFO main HConnectionManager$TableServers -
getMaster at tempt 6 of 10 failed; retrying after sleep of 4000".
Can't figure out where the problem lies.

Attaching the collector.log to this mail and below is my


<?xml version="1.0"?>
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   See the License for the specific language governing permissions and
   limitations under the License.
<?xml-stylesheet type="text/xsl"  href="configuration.xsl"?>

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



<!-- peetam: replaced by HBaseWriter pipeline below

<!-- LocalWriter parameters
    <description>Chukwa local data sink directory, see</description>

    <description>Local chukwa writer, see</description>

<!-- When writing to HBase, uncomment the following parameters. If
you're running
HBase in distributed mode, you'll also need to copy your
hbase-site.xml file with
your hbase.zookeeper.quorum setting to the conf/ dir. -->


    <description>Demux parser class package, HBaseWriter uses this
package name to validate HBase for annotated demux parser

    <description>Verify HBase Table schema with demux parser schema, log
    warning if there are mismatch between hbase schema and demux parsers.

    <description>If this option is set to true, and HBase table schema
    is mismatched with demux parser, collector will shut down itself.

    <description>HDFS to dump to</description>

    <description>Chukwa data sink directory</description>

    <description>Chukwa rotate interval (ms)</description>

    <description>The HTTP port number the collector will listen on</description>

On Wed, Jun 1, 2011 at 10:11 PM, Eric Yang <> wrote:
> From the current configuration, it is setup to write to Hbase only, it does
> not write to HDFS.  If you want the data to be written to HDFS as well, use
> this line in chukwa-collector-conf.xml.
>   <property>
>     <name>chukwaCollector.pipeline</name>
>     <value>org.apache.hadoop.chukwa.datacollection.writer.SocketTeeWriter,
> org.apache.hadoop.chukwa.datacollection.writer.hbase.HBaseWriter,
> org.apache.hadoop.chukwa.datacollection.writer.SeqFileWriter</value>
>   </property>
> Make sure that hadoop-site.xml and hbase-site.xml are in the chukwa
> collector class path.  This can be done by copying hadoop-site.xml and
> hbase-site.xml to CHUKWA_CONF_DIR.
> For HICC listening to localhost issue, this is a bug in Chukwa.  Feel free
> to file a jira.  Before compile, modify web/hicc/WEB-INF/jetty.xml and set
> ip address to  Without this setup, jetty would choose to
> bind to first available IP address, it could randomly bind to localhost or
> eth0 depending on the OS.
> Regards,
> Eric

View raw message