Hi Raymond, WAL Archive can be used for recovery during node restart. It can happen if WAL data during one checkpoint is longer than segmentSize*workSegments (640Mb by default).
The downside of not having archiver is following: Space allocation for a file may require significant time in some file systems. If we archive one WAL segment (asynchronously) we can later reuse this segment file in the work directory for a new segment records. The file is now preallocated, there will be no performance penalty for step by step increasing of its volume. Sincerely, Dmitriy Pavlov You can find scheme of WAL rotation here: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-WALstructure пн, 1 окт. 2018 г. в 22:21, Raymond Wilson <raymond_wil...@trimble.com>: > Hi, > > > > I’ve been reading through this page ( > https://apacheignite.readme.io/docs/write-ahead-log) on WAL files in > Ignite. > > > > I’d like to understand what the purpose of the WAL archive is. I > understand from the documentation that the WAL archive contains data that > has been checkpointed, and so safely committed to the cache partition files. > > > > It seems to be optional in that it is possible to not have one by setting > the WAL active and archive paths to be the same location. The documentation > recommends doing this if ingest volumes mean time spent copying WAL files > to the archive can cause node freezes. > > > > Is the WAL archive used in recovery operations when an Ignite node > restarts? Is there a downside to not having WAL segments archived? > > > > Thanks, > > Raymond. > > >
