Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 358A0D517 for ; Fri, 17 May 2013 11:40:53 +0000 (UTC) Received: (qmail 79022 invoked by uid 500); 17 May 2013 11:40:51 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 78383 invoked by uid 500); 17 May 2013 11:40:47 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 78352 invoked by uid 99); 17 May 2013 11:40:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 11:40:46 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yongyong313@gmail.com designates 209.85.160.54 as permitted sender) Received: from [209.85.160.54] (HELO mail-pb0-f54.google.com) (209.85.160.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 11:40:40 +0000 Received: by mail-pb0-f54.google.com with SMTP id ro8so3228799pbb.13 for ; Fri, 17 May 2013 04:40:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=FYCgSef2SkcMm9nw04NW5nk4JJtscF2dUs2fCVV6llI=; b=GpvSMap+TF3vGrVqWdKMFH0J98SImiM+Q3MGOiVlb4ZgaePsQBV92vBF/Yo95dL/NI bDxMSkzn4nEFmriCwpOp82Oxcph9J7BQNip+RTYWvuVGavc/QWgk9d0GcEXChH7cTGY5 0jCztazI/Zisy7n+9t8JuKCPdoWDuRWOSHKhR5gbdz5os29fz/iEhpJIZcErf4EP0r61 7+506IlkHQa53pBwBR08Ew8yGkyATSmNeHk1+FTpgIfK40gzYDRdU3lUuA9xGwbiTnMy drkVvprW5OCRWV4wW+mvOG89Xe0zAR8rXnpT0DoN1K/hz9r4IhSDgbMa7HjCu4lfLV8R VU/w== MIME-Version: 1.0 X-Received: by 10.66.162.229 with SMTP id yd5mr48134287pab.46.1368790819437; Fri, 17 May 2013 04:40:19 -0700 (PDT) Received: by 10.66.253.42 with HTTP; Fri, 17 May 2013 04:40:19 -0700 (PDT) In-Reply-To: References:

Date: Fri, 17 May 2013 13:40:19 +0200 Message-ID: Subject: Re: Doubt Regading HLogs From: yonghu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b86f22e90836a04dce8722a X-Virus-Checked: Checked by ClamAV on apache.org --047d7b86f22e90836a04dce8722a Content-Type: text/plain; charset=ISO-8859-1 In this situation, you can set the > > > hbase.regionserver. logroll.period > > 3600000 > > to a short value, let's say 3000 and then you can see your log file with current size after 3 seconds. To Nicolas, I guess he wants somehow to analyze the HLog. regards! Yong On Fri, May 17, 2013 at 1:27 PM, Rishabh Agrawal < rishabh.agrawal@impetus.co.in> wrote: > Thanks Nicolas, > > When will this file be finalized. Is it time bound? Or it will be always > be zero for last one (even if it contains the data) > > -----Original Message----- > From: Nicolas Liochon [mailto:nkeywal@gmail.com] > Sent: Friday, May 17, 2013 4:39 PM > To: user > Subject: Re: Doubt Regading HLogs > > That's HDFS. > > When a file is currently written, the size is not known, as the write is > in progress. So the namenode reports a size of zero (more exactly, it does > not take into account the hdfs block beeing written when it calculates the > size). When you read, you go to the datanode owning the data, so you see > the real content as it is at the time of reading. > > btw, why do you want to read the HLog? > > > On Fri, May 17, 2013 at 12:53 PM, Rishabh Agrawal < > rishabh.agrawal@impetus.co.in> wrote: > > > Hello, > > > > I am working with Hlogs of Hbase and I have this doubt that HDFS shows > > size of last log file as zero. But when I open it I see data in it. > > When I add extra data a new file with zero size is created and > > previous HLog file gets its size. This thing applies to each region > > server. Following is the purged screen shot of same: > > > > > > > > I have set following parameters in hbase-site.xml for logs: > > > > > > > > hbase.regionserver.logroll.period > > > > 3600000 > > > > > > > > > > > > hbase.master.logcleaner.ttl > > > > 604800000 > > > > > > > > > > > > hbase.regionserver.optionallogflushinterval > > > > 3000 > > > > > > > > > > > > > > > > I plan to read log files for some validation work, Please guide me > > through this behavior of Hbase. > > > > > > > > > > > > Thanks and Regards > > > > Rishabh Agrawal > > > > Software Engineer > > > > Impetus Infotech (India) Pvt. Ltd. > > > > (O) +91.731.426.9300 x4526 > > > > (M) +91.812.026.2722 > > > > www.impetus.com > > > > > > > > ------------------------------ > > > > > > > > > > > > > > NOTE: This message may contain information that is confidential, > > proprietary, privileged or otherwise protected by law. The message is > > intended solely for the named addressee. If received in error, please > > destroy and notify the sender. Any use of this email is prohibited > > when received in error. Impetus does not represent, warrant and/or > > guarantee, that the integrity of this communication has been > > maintained nor that the communication is free of errors, virus, > interception or interference. > > > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, > proprietary, privileged or otherwise protected by law. The message is > intended solely for the named addressee. If received in error, please > destroy and notify the sender. Any use of this email is prohibited when > received in error. Impetus does not represent, warrant and/or guarantee, > that the integrity of this communication has been maintained nor that the > communication is free of errors, virus, interception or interference. > --047d7b86f22e90836a04dce8722a--