Return-Path: Delivered-To: apmail-hadoop-chukwa-user-archive@minotaur.apache.org Received: (qmail 4456 invoked from network); 17 Mar 2010 04:11:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Mar 2010 04:11:15 -0000 Received: (qmail 52929 invoked by uid 500); 17 Mar 2010 04:11:15 -0000 Delivered-To: apmail-hadoop-chukwa-user-archive@hadoop.apache.org Received: (qmail 52856 invoked by uid 500); 17 Mar 2010 04:11:15 -0000 Mailing-List: contact chukwa-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: chukwa-user@hadoop.apache.org Delivered-To: mailing list chukwa-user@hadoop.apache.org Received: (qmail 52845 invoked by uid 99); 17 Mar 2010 04:11:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 04:11:14 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=MIME_QP_LONG_LINE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [69.147.107.21] (HELO mrout2-b.corp.re1.yahoo.com) (69.147.107.21) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 04:11:07 +0000 Received: from SNV-EXBH01.ds.corp.yahoo.com (snv-exbh01.ds.corp.yahoo.com [207.126.227.249]) by mrout2-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o2H48uYe042800 for ; Tue, 16 Mar 2010 21:08:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:user-agent:date:subject:from:to:message-id: thread-topic:thread-index:in-reply-to:mime-version:content-type: content-transfer-encoding:x-originalarrivaltime; b=YUGLgGJL2NerSk9rn0Xi8VbiXPhZx0uicULbLIlSBbZVnxrwCaa+2k7A3f4xTUzu Received: from SNV-EXVS06.ds.corp.yahoo.com ([207.126.227.234]) by SNV-EXBH01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Mar 2010 21:08:55 -0700 Received: from 10.72.168.87 ([10.72.168.87]) by SNV-EXVS06.ds.corp.yahoo.com ([207.126.227.82]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.60]) with Microsoft Exchange Server HTTP-DAV ; Wed, 17 Mar 2010 04:08:38 +0000 User-Agent: Microsoft-Entourage/12.24.0.100205 Date: Tue, 16 Mar 2010 21:08:37 -0700 Subject: Re: How to set up HDFS -> MySQL from trunk? From: Eric Yang To: Message-ID: Thread-Topic: How to set up HDFS -> MySQL from trunk? Thread-Index: AcrFh4SiOeY1K2fKFUKczmIMjklJfA== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-OriginalArrivalTime: 17 Mar 2010 04:08:55.0959 (UTC) FILETIME=[8FEFBA70:01CAC587] X-Virus-Checked: Checked by ClamAV on apache.org Chukwa use case is probably not effected by the decision on MAPREDUCE-1126. Chukwa key is composed of Long (time partition), String (primary key), Long (timestamp). The value is composed of Avro blob. I like to try out using Avro to serialize the comparator, but it makes no difference in Chukwa use case because it is likely that I have to write my own comparator to begin with for Tfile. I agree with Chris Douglas and Time White said, the Avro serializing comparator should be optional. I like Tim's example: Schema keySchema =3D ... AvroGenericData.setMapOutputKeySchema(job, keySchema); Hope this helps. Regards, Eric On 3/16/10 2:56 PM, "Jeff Hammerbacher" wrote: > Hey Eric, >=20 > Could you chime in on MAPREDUCE-815 with your potential use case? We're > currently blocked on other issues, but getting more use cases on the tabl= e > will be helpful. >=20 > Thanks, > Jeff >=20 > On Mon, Mar 15, 2010 at 7:41 PM, Eric Yang wrote: >> Hi Kirk, >>=20 >> The Avro + Tfile plan depends on >> https://issues.apache.org/jira/browse/MAPREDUCE-815. =A0The work can start >> once Avro Input/Out format patch is included in a release build of Hadoo= p. >> Hence, I would project to complete this migration would be at least six >> months from Avro Mapreduce ready. =A0It's a fair big chunk of work, and it >> would be great if people want to pitch in to build aggregator piece to >> control the workflow. =A0See https://issues.apache.org/jira/browse/CHUKWA-= 444 >> for reference. >>=20 >> Regards, >> Eric >>=20 >> On 3/15/10 3:03 PM, "Kirk True" wrote: >>=20 >>> Hi Eric, >>>=20 >>> Any notion as to the ETA for completion of the migration? >>>=20 >>> Thanks, >>> Kirk >>>=20 >>> Eric Yang wrote: >>>>=20 >>>> Hi Kirk, >>>>=20 >>>> I am working on a design which removes MySQL from Chukwa. =A0I am making= this >>>> departure from MySQL because MDL framework was for prototype purpose. = =A0It >>>> will not scale in production system where Chukwa could be host on larg= e >>>> hadoop cluster. =A0HICC will serve data directly from HDFS in the future= . >>>>=20 >>>> Meanwhile, the dbAdmin.sh from Chukwa 0.3 is still compatible with tru= nk >>>> version of Chukwa. =A0You can load ChukwaRecords using >>>> org.apache.hadoop.chukwa.dataloader.MetricDataLoader class or mdl.sh f= rom >>>> Chukwa 0.3. >>>>=20 >>>> MetricDataLoader class will be mark as deprecated, and it will not be >>>> supported once we make transition to Avro + Tfile. >>>>=20 >>>> Regards, >>>> Eric >>>>=20 >>>> On 3/15/10 11:56 AM, "Kirk True" >>>> =A0wrote: >>>>=20 >>>>=20 >>>>=20 >>>>>=20 >>>>> Hi all, >>>>>=20 >>>>> I recently switched to trunk as I was experiencing a lot of issues wi= th >>>>> 0.3.0. In 0.3.0, there was a dbAdmin.sh script that would run and try= to >>>>> stick data in MySQL from HDFS. However, that script is gone and when = I >>>>> run the system as built from trunk, nothing is ever populated in the >>>>> database. Where are the instructions for setting up the HDFS -> MySQL >>>>> data migration for HICC? >>>>>=20 >>>>> Thanks, >>>>> Kirk >>>>>=20 >>>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>=20 >>=20 >=20 >=20