Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <58421932.1207260564529.JavaMail.jira@brutus>
Date: Thu, 3 Apr 2008 15:09:24 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3146) DFSOutputStream.flush should be
 renamed as DFSOutputStream.fsync
In-Reply-To: <532577573.1207017864499.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HADOOP-3146:
-------------------------------------

    Attachment: flushToFsync2.patch

The previous patch did not change one unit test that was still invoking the old flush() API. 

> DFSOutputStream.flush should be renamed as DFSOutputStream.fsync
> ----------------------------------------------------------------
>
>                 Key: HADOOP-3146
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3146
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Runping Qi
>            Assignee: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: flushToFsync.patch, flushToFsync2.patch
>
>
> Starting fron hadoop-0.17, calling flush of dfs becomes very expensive.
> The current implementation of flush should be renamed as sync.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.