From notifications-return-7509-apmail-accumulo-notifications-archive=accumulo.apache.org@accumulo.apache.org Fri May 24 00:38:20 2013 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 343D9974C for ; Fri, 24 May 2013 00:38:20 +0000 (UTC) Received: (qmail 8753 invoked by uid 500); 24 May 2013 00:38:20 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 8695 invoked by uid 500); 24 May 2013 00:38:20 -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 8685 invoked by uid 99); 24 May 2013 00:38:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 May 2013 00:38:20 +0000 Date: Fri, 24 May 2013 00:38:20 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-118) accumulo could work across HDFS instances, which would help it to scale past a single namenode 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-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665879#comment-13665879 ] Josh Elser commented on ACCUMULO-118: ------------------------------------- {quote} With a different viewfs implementation, we could use a hash to determine the namespace and hide the whole switch between file systems: hash("/accumulo/tables/1/default_tablet/A0003892.rf") % 2 -> hdfs://nn1:12345 hash("/accumulo/tables/1/default_tablet/F0004567.rf") % 2 -> hdfs://nn2:12345 Unfortunately, renaming a file might force it to a new namespace. {quote} I bet you could be tricky with that actual hash+modulo in such a way which guarantees that it wouldn't change namespaces. > accumulo could work across HDFS instances, which would help it to scale past a single namenode > ---------------------------------------------------------------------------------------------- > > Key: ACCUMULO-118 > URL: https://issues.apache.org/jira/browse/ACCUMULO-118 > Project: Accumulo > Issue Type: Improvement > Components: master, tserver > Reporter: Eric Newton > Assignee: Eric Newton > Priority: Blocker > Fix For: 1.6.0 > > Attachments: ACCUMULO-118-01.txt > > Original Estimate: 2,016h > Remaining Estimate: 2,016h > > Consider using full path names to files, which would allow the servers to access the files on any HDFS file system. > Work may exist elsewhere to run HDFS using a number of NameNode instances to break up the namespace. > We may need a pluggable strategy to determine namespace for new files. -- 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