Hello! I guess it is the time to iterate WAL after the last checkpoint to make sure all operations prior to node stop are accounted for.
Every DB will do that and the time of 76 seconds seems reasonable. Regards, -- Ilya Kasnacheev вт, 29 сент. 2020 г. в 02:00, Raymond Wilson <[email protected]>: > There is a summary log line that also references the time taken by the > 'restore binary memory' stage. It also references another stage called > 'restore logical state'. > > eg: > > 2020-09-27 20:50:31,423 [1] INF [] Node started : [stage="Configure system > pool" (44 ms),stage="Start managers" (2422 ms),stage="Configure binary > metadata" (487 ms),stage="Start processors" (1089 ms),stage="Init > metastore" (726 ms),stage="Init and start regions" (21 ms),stage="Restore > binary memory" (30289 ms),stage="Restore logical state" (76551 > ms),stage="Finish recovery" (201 ms),stage="Join topology" (840 > ms),stage="Await transition" (136 ms),stage="Await exchange" (211 > ms),stage="Total time" (113017 ms)] > > The restore logical state stage takes 76 seconds in this example. > > Currently we have around 10 caches with less than 20 Gb of data. Do these > startup times seem reasonable for a node that is shut down gracefully? > > Thanks, > Raymond. > > > On Tue, Sep 29, 2020 at 11:20 AM Raymond Wilson < > [email protected]> wrote: > >> Just a general query on Ignite server node startup sequence. >> >> There are a pair of log lines emitted during node startup that look like >> this: >> >> 2020-09-27 20:48:43,191 [1] INF [] Starting binary memory restore for: >> [948695530, -1026154091, -2049124072, -552847479, -2024686410, -1820754607, >> -1907049797, -1029472048, 671082124, -493080817, -2100569601, 928822533] >> >> >> and >> >> 2020-09-27 20:49:13,025 [1] INF [] Binary memory state restored at >> node startup [restoredPtr=FileWALPointer [idx=1033, fileOff=485201080, >> len=0]] >> >> This particular example required ~30 seconds to complete. >> >> We are running Ignite 2.8.1 using the C# client with persistence enabled. >> >> Do these messages indicate Ignite is reloading the memory state of the >> caches at the point it was shutdown? If not, what is this activity? >> >> Thanks, >> Raymond. >> >> -- >> <http://www.trimble.com/> >> Raymond Wilson >> Solution Architect, Civil Construction Software Systems (CCSS) >> 11 Birmingham Drive | Christchurch, New Zealand >> +64-21-2013317 Mobile >> [email protected] >> >> >> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch> >> > > > -- > <http://www.trimble.com/> > Raymond Wilson > Solution Architect, Civil Construction Software Systems (CCSS) > 11 Birmingham Drive | Christchurch, New Zealand > +64-21-2013317 Mobile > [email protected] > > > <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch> >
