Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <46937477.1223921684718.JavaMail.jira@brutus>
Date: Mon, 13 Oct 2008 11:14:44 -0700 (PDT)
From: "Pete Wyckoff (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4399)  fuse-dfs per FD context is not
 thread safe and can cause segfaults and corruptions
In-Reply-To: <1640347182.1223859404200.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-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Wyckoff updated HADOOP-4399:
---------------------------------

    Priority: Blocker  (was: Major)

>  fuse-dfs per FD context is not thread safe and can cause segfaults and corruptions
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-4399
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4399
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fuse-dfs
>    Affects Versions: 0.19.0
>            Reporter: Pete Wyckoff
>            Assignee: Pete Wyckoff
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-4399.1.txt
>
>
> for reads, optimal solution would be to have a per thread (per FD) context - including the buffer. Otherwise, protect the FD context with a mutex as in hadoop-4397 and hadoop-4398.
> for writes, should just protect the context with a mutex as in hadoop-4398.

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