Thx Ivan, that helps On May 16, 2017 10:24 AM, "Ivan Veselovsky" <[email protected]> wrote:
Hi, Pranay, > Does it mean that Namenode can be avoided when IGFS get deployed on top of > HDFS ? No. IGFS itself does not have namenode, it is a distributed cache storing file blocks. But when deployed on top of HDFS, it fetches the underlying data using ordinary namenode mechanism. > Or is it that when one reads from IGFS (for mapreduce or only data ), > there is nothing like a namenode .... but for IGFS to talk to HDFS, > namenode is still needed. Yes. > But now, when we access the same data, it can be accessed from IGFS > directly and there is no need of a namenode. Yes, if the requested data were fully cached, it will be given to the client w/o namenode access. -- View this message in context: http://apache-ignite-users. 70518.x6.nabble.com/HDFS-IGFS-Integration-tp12874p12891.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
