Description

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.

@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.

Sriram Rao
added a comment - 22/Sep/08 21:19 @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.

Hadoop QA
added a comment - 23/Sep/08 00:19 -1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12390672/patch.4234
against trunk revision 697306.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
-1 patch. The patch command could not apply the patch.
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3347/console
This message is automatically generated.

Sriram Rao
added a comment - 23/Sep/08 07:45 Providing a new patch since the previous one didn't work.
Re: no new test, this issue was found in a KFS deployment. To test this code path, a KFS+Hadoop deployment is required; that was done elsewhere.