Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 15E3E100BB for ; Mon, 15 Jul 2013 20:30:56 +0000 (UTC) Received: (qmail 1548 invoked by uid 500); 15 Jul 2013 20:30:55 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 1514 invoked by uid 500); 15 Jul 2013 20:30:55 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 1506 invoked by uid 99); 15 Jul 2013 20:30:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jul 2013 20:30:55 +0000 Date: Mon, 15 Jul 2013 20:30:55 +0000 (UTC) From: "Noah Watkins (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-6253) Add a Ceph FileSystem interface. 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/HADOOP-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708940#comment-13708940 ] Noah Watkins commented on HADOOP-6253: -------------------------------------- Hi Steve, Noah, I've been doing work in HADOOP-9361 both with trying to specify more I'd be happy to! One of the biggest things we have run into is figuring out what the contract is. Inferring it from the behavior of applications has been our only real resource for that information. We have done some ad-hoc stuff in which we have adapted HDFS tests to run against Ceph, but it is pretty ugly and difficult to maintain. One thing that we have run into recently with a user is diagnosing some write performance problems. HDFS is performing well, and we think small writes might be a culprit if Ceph isn't doing write buffering. Understanding what that contract is, especially in terms of write safety is another area slightly different than just unit tests that we are interested in. Ahh, that would be cool. Certainly easier to merge changes to that than accept an entire new file system upstream :) Let me know how I get can started helping out. -Noah > Add a Ceph FileSystem interface. > -------------------------------- > > Key: HADOOP-6253 > URL: https://issues.apache.org/jira/browse/HADOOP-6253 > Project: Hadoop Common > Issue Type: New Feature > Components: fs > Reporter: Gregory Farnum > Assignee: Gregory Farnum > Priority: Minor > Labels: ceph > Attachments: HADOOP-6253.patch, HADOOP-6253.patch, HADOOP-6253.patch, HADOOP-6253.patch, HADOOP-6253.patch > > > The experimental distributed filesystem Ceph does not have a single point of failure, uses a distributed metadata cluster instead of a single in-memory server, and might be of use to some Hadoop users. > http://ceph.com/docs/wip-hadoop-doc/cephfs/hadoop/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira