ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Fwd: IGFS backed by persistence on physical filesystem
Date Tue, 17 Nov 2015 20:24:37 GMT
Moving this discussion to the dev list.

As far as I know, IGFS stores data in blocks, so one file can be
distributed across nodes. So I don't see how each node can persist locally.
In my understanding it should be designated shared directory where all
files are persisted. This is actually analogous to how our persistence
store works for regular cache data.

Ivan, correct me if I'm wrong.


---------- Forwarded message ----------
From: Ivan Veselovsky <iveselovskiy@gridgain.com>
Date: Tue, Nov 17, 2015 at 11:48 AM
Subject: Re: IGFS backed by persistence on physical filesystem
To: user@ignite.apache.org

Paolo Di Tommaso wrote
> What if you have multiple nodes in a cluster using
> org.apache.hadoop.fs.LocalFileSystem as a secondary file system? Each node
> saves the IGFS content locally?

In my understanding yes, each node that was requested to do the file
operation will store the file locally.

Paolo Di Tommaso wrote
> Could it be used to save the data over a NFS mount ?

LocalFileSystem runs over OS file system with "/" being the roott of the
file system, so if an NFS path is mounted , say, in /mnt/nfs/, the files
written under there will be shared. We may think about some kind of "chroot"
there to isolate the Ignite file system from other things.

View this message in context:
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message