Return-Path: Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: (qmail 91850 invoked from network); 25 Jan 2010 06:36:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 06:36:35 -0000 Received: (qmail 52125 invoked by uid 500); 25 Jan 2010 06:36:35 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 52023 invoked by uid 500); 25 Jan 2010 06:36:34 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 52014 invoked by uid 99); 25 Jan 2010 06:36:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 06:36:34 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gokulm@huawei.com designates 119.145.14.66 as permitted sender) Received: from [119.145.14.66] (HELO szxga03-in.huawei.com) (119.145.14.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 06:36:27 +0000 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KWS00HGVIC5Q7@szxga03-in.huawei.com> for hdfs-user@hadoop.apache.org; Mon, 25 Jan 2010 14:36:05 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KWS00HXTIC5SU@szxga03-in.huawei.com> for hdfs-user@hadoop.apache.org; Mon, 25 Jan 2010 14:36:05 +0800 (CST) Received: from BLRNSHTIPL6NC ([10.18.1.36]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KWS00AH9IC4KZ@szxml06-in.huawei.com> for hdfs-user@hadoop.apache.org; Mon, 25 Jan 2010 14:36:05 +0800 (CST) Date: Mon, 25 Jan 2010 12:06:04 +0530 From: Gokulakannan M Subject: Reg HDFS 278 , HADOOP 6099 , HDFS 200 To: hdfs-user@hadoop.apache.org Reply-to: gokulm@huawei.com Message-id: <000001ca9d88$ab831c90$2401120a@china.huawei.com> Organization: htipl MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.3168 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/alternative; boundary="Boundary_(ID_GU11X+9Vmd6yFpVl7zweeA)" Thread-index: AcqdiKrxhc1ZIWLqRFio78RBqPnH/Q== This is a multi-part message in MIME format. --Boundary_(ID_GU11X+9Vmd6yFpVl7zweeA) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, I'm able to write logs into HDFS (hadoop 0.20.1 release) using Scribe2.1 In many sites(particularly in dhurba's post) I've noticed that, for Scribe-HDFS integration, these patches must be applied. But I didn't apply any of them. It is still working fine(I didn't notice any bugs yet!!). My question is that "What will be the side effects if I don't apply those patches? Will there be any problem in real time?" Thanks, Gokul --Boundary_(ID_GU11X+9Vmd6yFpVl7zweeA) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

Hi,

I'm able to write logs into HDFS (hadoop 0.20.1 release) using Scribe2.1

In many sites(particularly in dhurba's post) I've noticed that, for Scribe-HDFS integration, these patches

<HDFS 278 , HADOOP 6099 , HDFS 200> must be applied.

But I didn't apply any of them. It is still working fine(I didn't notice any bugs yet!!).

My question is that "What will be the side effects if I don't apply those patches? Will there be any problem in real time?"

Thanks,

Gokul

--Boundary_(ID_GU11X+9Vmd6yFpVl7zweeA)--