Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1597088221.1222114784312.JavaMail.jira@brutus>
Date: Mon, 22 Sep 2008 13:19:44 -0700 (PDT)
From: "Sriram Rao (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4234) KFS: Allow KFS layer to interface
 with multiple KFS namenodes
In-Reply-To: <822148660.1222028624160.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-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633471#action_12633471 ] 

Sriram Rao commented on HADOOP-4234:
------------------------------------

@Tsz: In the patch that is submitted, in the Init() method, we don't need to check whether kfsImpl == null.  The KFS client library code keeps track of all the servers to which the client is connected to; it build a new "handle" for each new server.

> KFS: Allow KFS layer to interface with multiple KFS namenodes
> -------------------------------------------------------------
>
>                 Key: HADOOP-4234
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4234
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>            Reporter: Sriram Rao
>            Assignee: Sriram Rao
>            Priority: Minor
>             Fix For: 0.19.0
>
>         Attachments: patch.4234
>
>
> The KFS "glue" layer code in Hadoop, currently, only allows an application to interface with a single KFS namenode.  The KFS client side library has been modified to allow applications to interface with multiple KFS namenodes.  This jira issue is for incorporating the change into the KFS code.  

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