We are deploying an Ignite application to a Kubernetes cluster in AWS EKS and are planning to use EFS for persistent data.
I have been reading through the tuning options for the Write Ahead Log Archive, trying to understand if we can safely turn off the archive to save the IO related to copying a WAL segment to the archive when it is full. As far as I can tell, the only functional role of the archived segments compared to the segments present in the write ahead log is to save potential file system slowness in recreating new segments compared to overwriting an existing segment once it has been copied to the archive. Apart from this, a WAL with 10 segments seems to provide the same consistency guarantees in the event of failure as a WAL with one active segment and a WAL archive with 10 archived segments. As we are using EFS we do not have issues with disk space so can define an arbitrarily large WAL without the need to copy these files to a separate archive which will contend the EFS bandwidth even if copies asynchronously within Ignite. Is my understanding correct here with respect to the EFS use case? Thanks, Raymond. -- <http://www.trimble.com/> Raymond Wilson Solution Architect, Civil Construction Software Systems (CCSS) 11 Birmingham Drive | Christchurch, New Zealand
