Return-Path: Delivered-To: apmail-hadoop-chukwa-dev-archive@minotaur.apache.org Received: (qmail 61670 invoked from network); 18 Dec 2009 01:27:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 01:27:32 -0000 Received: (qmail 40008 invoked by uid 500); 18 Dec 2009 01:27:32 -0000 Delivered-To: apmail-hadoop-chukwa-dev-archive@hadoop.apache.org Received: (qmail 39965 invoked by uid 500); 18 Dec 2009 01:27:31 -0000 Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: chukwa-dev@hadoop.apache.org Delivered-To: mailing list chukwa-dev@hadoop.apache.org Received: (qmail 39955 invoked by uid 99); 18 Dec 2009 01:27:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 01:27:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of asrabkin@gmail.com designates 209.85.221.187 as permitted sender) Received: from [209.85.221.187] (HELO mail-qy0-f187.google.com) (209.85.221.187) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 01:27:22 +0000 Received: by qyk17 with SMTP id 17so1258570qyk.2 for ; Thu, 17 Dec 2009 17:27:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:references; bh=AFtKE4DMQ9eHtoc4wH8Hi4yzjWVrTwpTdy22+jfKh4w=; b=xI+uQAZid6xu6pGnmaVL2J/Uwtb79XTvh531Ry+yDHAEfZ4dE9/6kAdMmxKfiuVrAr p5ok3b9jUPjH0D0Hw9STDu0Ipe9gzH2T3HWLsb0NQgQrD+4W/ax+MWu+Bjmo2t6vuwzP eJNvGBI95FuTVNvzv/Zu78WPjCSUZS/JT+pnQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date :references; b=EKfuBlKm13EDrIkwoO5ZW9gNICB+1MMmzvamtZqSx/13J1Erk2K+xLd9bZ3CSbLeST b/P3DDMYzQXbzZUXgRSLOQw95koNe+Y79JyYg+x0uIBZyf9bb5RH0+vcKBOxeq218llf SwPnQCzmEFvZczv3uIlQuKFxZJnlfS4AZD/ww= Received: by 10.229.61.28 with SMTP id r28mr1807754qch.10.1261099621662; Thu, 17 Dec 2009 17:27:01 -0800 (PST) Received: from ?10.17.197.38? (mobile-166-137-137-178.mycingular.net [166.137.137.178]) by mx.google.com with ESMTPS id 23sm1879988qyk.3.2009.12.17.17.26.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Dec 2009 17:27:00 -0800 (PST) Message-Id: From: asrabkin@gmail.com To: "chukwa-dev@hadoop.apache.org" In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7D11) Mime-Version: 1.0 (iPhone Mail 7D11) Subject: Re: PipelineStageWriter doesn't work as expected Date: Thu, 17 Dec 2009 20:26:51 -0500 References: X-Virus-Checked: Checked by ClamAV on apache.org Put the SocketTeeWriter first. sent from my iPhone; please excuse typos and brevity. On Dec 17, 2009, at 8:12 PM, Eric Yang wrote: > Hi all, > > I'd setup SocketTeeWriter by itself, and having data stream to next > socket > reader program. When I tried to configure two writers, i.e., > SeqFileWriter > follow by SocketTeeWriter. It doesn't work because SeqFileWriter > isn't > extending PipelineableWriter. I went ahead to extend SeqFileWriter as > PipelineableWriter and do that and implemented setNextStage method, > and > configured collector with: > > > chukwaCollector.writerClass > > > org.apache.hadoop.chukwa.datacollection.writer.PipelineStageWriter alue> > > > > chukwaCollector.pipeline > > > org.apache.hadoop.chukwa.datacollection.writer.SeqFileWriter,org.apac > he.hadoop.chukwa.datacollection.writer.SocketTeeWriter > > > SeqFileWriter writes the data correctly, but when connect to > SocketTeeWriter, there was no data visible in SocketTeeWriter. > Commands > works fine, but data streaming doesn't happen. How do I configure the > collector and PipelineStageWriter to be able to write data into > multiple > writer? Is there something on SeqFileWriter that could prevent this > from > working? > > Regards, > Eric >