hi , I am new to Ignite and have been exploring the usage of ignite as a caching layer with HDFS filesystem underneath - There was a mention that there was no need of a namenode using IGFS as it can determine the file data locality using the hashing function. Does it mean that Namenode can be avoided when IGFS get deployed on top of HDFS ? If that's true, can someone please give me an example where such a configuration is done ? 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.
Example.... assume that data is in HDFS initially.... Now when we read the data, it comes in IGFS and gets cached ( but in this case namenode was used, the regular behaviour )... But now, when we access the same data, it can be accessed from IGFS directly and there is no need of a namenode. thanks for your help - thx pranay
