Re: Support for non-HDFS distributed, shared POSIX FS

2010-07-01 Thread Chris D
With the following configuration, tasks complete successfully: 1. /mnt1 is the mount point for a shared, distributed FS on all machines running hadoop. 2. hadoop.tmp.dir = /mnt1/tmp/hadoop 3. fs.default.name = file:/// 4. `bin/hadoop jar hadoop-*-examples.jar wordcount /mnt1/input /mnt1/ouput` top

Re: Support for non-HDFS distributed, shared POSIX FS

2010-07-01 Thread Allen Wittenauer
On Jul 1, 2010, at 12:00 PM, Chris D wrote: > Yes, it is mountable on all machines simultaneously, and, for example, works > properly through file:///mnt/to/dfs in a single node cluster. Then file:// will likely work a multi-node cluster as well. So I doubt you'll need to write anything at a

Re: Support for non-HDFS distributed, shared POSIX FS

2010-07-01 Thread Chris D
Yes, it is mountable on all machines simultaneously, and, for example, works properly through file:///mnt/to/dfs in a single node cluster. On Jul 1, 2010 11:51 AM, "Allen Wittenauer" wrote: On Jul 1, 2010, at 11:28 AM, Chris D wrote: > In the new URI I seek to create, each MapReduce slave... If

Re: Support for non-HDFS distributed, shared POSIX FS

2010-07-01 Thread Allen Wittenauer
On Jul 1, 2010, at 11:28 AM, Chris D wrote: > In the new URI I seek to create, each MapReduce slave would look for input > data from a seemingly local file:///, and write output to it as well. Assume > that the distributed FS handles concurrent reads, writes. Assuming > POSIX-compliance, the Local

Support for non-HDFS distributed, shared POSIX FS

2010-07-01 Thread Chris D
Hi all, I’d like to create a new URI for a distributed POSIX-compliant filesystem shared between all nodes. A number of such filesystems currently exist (think HDFS w/o the POSIX incompliance). We can, of course, run HDFS on top of such a file system, but it adds an extra unnecessary and ineffic