Anyone know if it has the same single point of failure issues as HDFS (NameNode)?
Also, bummer that it's written in Java. I know that was for easy pluggability into Hadoop, but it makes it tough to write bindings for other languages.
I guess using non-native API would introduce significant overhead and kill all the advantages of using this Tachyon filesystem.
I take it, the resulting DFS can't be mounted, am I right? If yes, that's a pity. By the way, are there DFS with similar properties (very fast, aggressive memory use) that can be mounted?
> Anyone know if it has the same single point of failure issues as HDFS (NameNode)?
I think the NameNode SPOF issue in HDFS is also being dealt with:
"Prior to Hadoop 2.0.0, the NameNode was a single point of failure (SPOF) in an HDFS cluster.
[...] The HDFS High Availability feature addresses the above problems by providing the option of running two redundant NameNodes [...]"
Always cool to see different DFS options out there. That said, I personally won't find this very useful. It does not appear to have any POSIX support and thus only would work as a API/library accessible storage share. Hadoop at least has ways of mounting, although I personally haven't used them.
Wow, so bottom line
1. useful for Streaming cause of the nature of the file system.
2. Probably will loose the append nature of HDFS.
3. Retaining data in memory makes it hard to use with any of the hdfs based databases like hbase.
So raw map reducers should definately try it...
Also, bummer that it's written in Java. I know that was for easy pluggability into Hadoop, but it makes it tough to write bindings for other languages.