Yes, you are right, hashes for 00.wal and 01.wal are different before/after
load test
(last-modified-time still showing june 15th)
BEFORE
PS F:\ignite-wal\V_HP_LK_DCN01> get-filehash .\*
Algorithm Hash
-
SHA256
40A373D58ADF4C9E15B3F0969ED3B5E4D52AC24BC807AD9C8EE4F92982B7
I suppose that is issue with updating timestamps, rather with WAL writes.
Try to make a load test and compare hash sum of files before load test and
after. Also check if WAL history grow.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
WAL mode is default one, all caches are FULL_ASYNC
...and now I see one of my Ignite servers updated WAL files but other one
still have 19th last-modification-time
it looks like WAL files are updated once per day
Hi,
What is your configuration? Check WAL mode and path to persistence.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Ignite team,
I noticed that nothing is written into WAL files even on Ignite restart.
My testing steps:
1) bounce application and ignite cluster
2) perform load testing
3) bounce application and ignite cluster
4) check ignite files:
data files have recent modification time - OK
latest WAL f