Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30EEED867 for ; Thu, 1 Nov 2012 17:40:24 +0000 (UTC) Received: (qmail 60196 invoked by uid 500); 1 Nov 2012 17:40:19 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 59913 invoked by uid 500); 1 Nov 2012 17:40:18 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 59894 invoked by uid 99); 1 Nov 2012 17:40:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 17:40:18 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of doducthanhbk@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qc0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 17:40:10 +0000 Received: by mail-qc0-f176.google.com with SMTP id n41so2133322qco.35 for ; Thu, 01 Nov 2012 10:39:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=BDc/6Dw3LBV5+dQjd/hRbgZJsKDmWBsBEHTZULCKToY=; b=H1R9nXNySNR7VyBC6av8PhgmgSolGdTxua8K6srHWOWNQN6iKnV2u6oU4JWxhhBgp0 sEExg0G5WlY21/sYTzvAMFM1QuzgNkB6jiPvJvo9fxxmOXCTBep9x2o49WNS7wuWZY90 RPJpNh6oT5fqbtcx7w1DLoR30Y3EwoCPPSuo4H6IThSa4XeesFpAu5ej+pxKmoiQrKg0 OLyxk/lFUQrjFE/ya0aK3YmJj7T1YdoDFfnaQCkAiayOarO4kx/9c4SzuIOM3rW7OPqJ 0cIUknKmk4YVSDSqfi2AEoE6qedSM+/ZLCggWfAqE6C1gn0RWA+aYFbkxKRc2oCZT0yl OoOw== MIME-Version: 1.0 Received: by 10.224.182.203 with SMTP id cd11mr1887325qab.22.1351791589162; Thu, 01 Nov 2012 10:39:49 -0700 (PDT) Sender: doducthanhbk@gmail.com Received: by 10.49.106.234 with HTTP; Thu, 1 Nov 2012 10:39:49 -0700 (PDT) Date: Thu, 1 Nov 2012 12:39:49 -0500 X-Google-Sender-Auth: HXOwwiWyjHzzrW_zi9VNJLL-waE Message-ID: Subject: SequenceFile syncFs behavior? From: Thanh Do To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf302ef8c27b7d2f04cd728181 X-Virus-Checked: Checked by ClamAV on apache.org --20cf302ef8c27b7d2f04cd728181 Content-Type: text/plain; charset=UTF-8 Hi all, Could somebody clarify me the behavior of SequenceFile.syncFs(). From the source, I saw this function is deprecated, and hsync() or hflush() is recommended? However, it seems like current stable release of HBase (0.94) or the cloudera distribution (4.0) uses syncFs for its HLog file. Would syncFs() guarantee data durability? I am using hadoop 2.0. Many thanks, Thanh Do --20cf302ef8c27b7d2f04cd728181 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all,=C2=A0

Could somebody clarify me the behavior of = SequenceFile.syncFs().=C2=A0From the source, I saw this function is depreca= ted, and hsync() or hflush() is recommended? However, it seems like current= stable release of HBase (0.94) or the cloudera distribution (4.0) uses syn= cFs for its HLog file.=C2=A0

Would syncFs() guarantee data durability?
I am using hadoop 2.0.

Many thanks,
Thanh Do

--20cf302ef8c27b7d2f04cd728181--