I have some questions of deploying IGFS as a cache layer given that ignite could be deployed both as a key-value store and as a file system
1. How does IGFS behave when deployed in standalone mode? I wanted to confirm that there is no durability in this mode. Assuming I persist a parquet file on IGFS, if the cluster goes down I lose the file, right? 2. Do we get the ability to specify the fact that the file stored in IGFS could be both partitioned (with backup nodes) or replicated? 3. IGFS can act as a cache layer over HDFS and local file system, can it act as a caching layer over S3 store? 4. As with the key-value store, can I configure tiered storage in IGFS i.e. given that IGFS is configured with local file system as the secondary store and the ignite cluster of 3 server nodes configured with 5GB memory each, would the data spill over to the local disk if I try to load a 25GB file into IGFS? If so, what is the configuration needed? 5. Can I configure local SSD disks as the secondary store for IGFS? 6. I browsed through the documentation but I didn't find the capability of pinning and unpinning files in IGFS. I am looking something similar to what alluxio <http://www.alluxio.org/docs/master/en/Tiered-Storage-on-Alluxio.html#pinning-files> provides. Can it be implemented? 7. Could you elaborate a bit on how IGFS Proxy Mode works? What is its recommended use case? 8. With DUAL_ASYNC (write-behind mode), does ignite have failover guarantees which is lacking in the key-value store - https://issues.apache.org/jira/browse/IGNITE-1897? Thanks in advance. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IGFS-Questions-tp10217.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
