Return-Path: X-Original-To: apmail-incubator-chukwa-user-archive@www.apache.org Delivered-To: apmail-incubator-chukwa-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 708DC6EE4 for ; Fri, 15 Jul 2011 16:23:06 +0000 (UTC) Received: (qmail 38895 invoked by uid 500); 15 Jul 2011 16:23:06 -0000 Delivered-To: apmail-incubator-chukwa-user-archive@incubator.apache.org Received: (qmail 38793 invoked by uid 500); 15 Jul 2011 16:23:05 -0000 Mailing-List: contact chukwa-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: chukwa-user@incubator.apache.org Delivered-To: mailing list chukwa-user@incubator.apache.org Received: (qmail 38786 invoked by uid 99); 15 Jul 2011 16:23:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jul 2011 16:23:04 +0000 X-ASF-Spam-Status: No, hits=1.9 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eric818@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-iw0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jul 2011 16:22:55 +0000 Received: by iwn4 with SMTP id 4so1268766iwn.6 for ; Fri, 15 Jul 2011 09:22:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=E5kWGXid8OpD0jm7iO+dCV/vgSZTyxaMv7DzMCN9PN8=; b=XR+EeVuiuXNKk3LIJb6RdAMNz2zwde1N4NMUZspsdJvVhPWZZjijurSdqHMj7GQVpy pSrlJSuV+up2h+N708qg6s0dCED05cvW9yZ9yNjjSq0YBEfkYeliTEU3tKxf7zsqmvn2 PCdR5YsNvfFML0g4/4QjRo6U63t8KRSIAuilI= Received: by 10.42.131.2 with SMTP id x2mr3751260ics.259.1310746954990; Fri, 15 Jul 2011 09:22:34 -0700 (PDT) Received: from [10.10.10.121] ([70.35.59.2]) by mx.google.com with ESMTPS id d8sm1554156icy.9.2011.07.15.09.22.32 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jul 2011 09:22:33 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Multiple agents and multiple clusters From: Eric Yang In-Reply-To: Date: Fri, 15 Jul 2011 09:22:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <782B9D02-9525-49C3-82E4-2667A621DC27@gmail.com> References: To: chukwa-user@incubator.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org The data is written locally on the source node. Both agents will = progress independently, and sending data at their own pace to the = collectors. They shouldn't affect each other. The = UTF8FileTailingAdaptor should track the timestamp of the log files and = send it over in time sequence order, hence one failed does not affect = others. regards, Eric On Jul 14, 2011, at 8:45 PM, highpointe wrote: > Ahhhh. Good insight. I didn't think about that. >=20 > Yes, I am aggregating the same data for two clusters. =20 >=20 > So now my challenge is: If one cluster is unreachable... How do I = that cluster's sender fail without affecting the other sender or the = connector.=20 >=20 > Excellent insight Ari! Thank you! >=20 > Sent from my iPhone >=20 > On Jul 14, 2011, at 11:54 AM, Ariel Rabkin wrote: >=20 >> Just to be clear -- you want the same data to end up in each cluster? >>=20 >> You'll have to do some hacking. I think it won't be so very = monstrous. >> In the Agent, there's a notion of pluggable Connectors and Senders. I >> think you want a new Connector with two senders. >>=20 >> One caveat -- you'll need to think through what happens if just one >> cluster is down, and perhaps other partial failure scenarios too. >>=20 >> --Ari >>=20 >> On Thu, Jul 14, 2011 at 10:44 AM, high pointe = wrote: >>> I have a situation where I need to take the one data stream, send it = through >>> two agents and have the end point residing in separate clusters. >>> Rough explanation.... >>> Streaming Data Box ---> Chukwa Box >>> Agent one on Chukwa Box sends feed to cluster one. >>> Agent two on Chukwa box sends feed to cluster two. >>> Does anyone know of a way to do this without hacking this baby to = shreds? >>>=20 >>> Thanks! >>=20 >>=20 >>=20 >> --=20 >> Ari Rabkin asrabkin@gmail.com >> UC Berkeley Computer Science Department