Hi, Shiva! Yes, this ticket will only be about moving WAL archive cleanup. I think further it is possible to solve the problem of WAL archive overflow, but before that we need to solve several problems and deal with heuristics.
09.12.2020, 15:02, "shm" <shivakumar....@gmail.com>: > Hi Kirill Tkalenko > > Is this ticket is just for moving WAL archive clean-up logic from "post > checkpoint" to FileWriteAheadLogManager#rollOver ? Or is there any plan to > change the logic which considers Archived WAL segments for clean-up ? > > I'm facing a Major issue related to WAL usage and WAL usage growing > infinitely with heavy write load even maxWalArchiveSize is set. > > Ref: > http://apache-ignite-users.70518.x6.nabble.com/Could-not-clear-historyMap-due-to-WAL-reservation-on-cp-td34779.html > > http://apache-ignite-users.70518.x6.nabble.com/connecting-to-visor-shell-permanently-stops-unwanted-WAL-clean-up-td34737.html > > Shiva > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
