Hi,
You may use it in cases when you use temporary files that should be removed
after node stop, or any other data that don't require persistence.
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/NameNode-sync-using-DUAL-ASYNC-mode-on-IGFS-tp11644p11756
Hi Dmitriy,
Thanks for explaining. I understand.
In situations using Name node, it's better to use DUAL_SYNC mode.
May I ask one more?
> Basically it means that every time a data is changed in Ignite, it will also
> be changed in the underlying HDFS, either synchronously or asynchronously,
> b
Hi Massayuki,
Ignite itself does not have a concept of a NameNode. It goes directly to
the cluster node responsible for storing the data based on a key's hashcode.
The only time when a NameNode would come into a play, is when Hadoop HDFS
is configured as an underlying write-through file system. B
Hi,
I am trying to use IGFS on HDFS.
If I set DUAL_ASYNC to IGFS mode and execute 'hdfs dfs -put ...', when
does the file info write to HDFS NameNode?
Also, if I set PRIMARY to IGFS mode and put a new file, does the file
info write to HDFS NameNode?
thanks.
--
Masayuki Takahashi
