Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0972EF503 for ; Fri, 25 Apr 2014 17:51:58 +0000 (UTC) Received: (qmail 61590 invoked by uid 500); 25 Apr 2014 17:51:48 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 61532 invoked by uid 500); 25 Apr 2014 17:51:47 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 61241 invoked by uid 99); 25 Apr 2014 17:51:40 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 17:51:40 +0000 Date: Fri, 25 Apr 2014 17:51:40 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2452) DfsLogger.write(LogFileKey, LogFileValue) flushes with every call MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-2452: ---------------------------------------- Fix Version/s: (was: 1.6.0) > DfsLogger.write(LogFileKey, LogFileValue) flushes with every call > ----------------------------------------------------------------- > > Key: ACCUMULO-2452 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2452 > Project: Accumulo > Issue Type: Sub-task > Components: tserver > Reporter: Eric Newton > Assignee: Eric Newton > > I was reviewing {{DfsLogger}} today and explaining how it works. I noticed that every write of every event calls {{flush()}} on output file. This should be unnecessary since the flush thread should do all the flush/sync operations. It may be necessary for the encryption stuff, but we'll need to figure out some sort of alternative implementation for non-encrypted output. -- This message was sent by Atlassian JIRA (v6.2#6252)