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
40A373D58ADF4C9E15B3F0969ED3B5E4D52AC24BC807AD9C8EE4F92982B71925
SHA256
DE2B96517256C844524CD9A1C4ED8EDE18FA92440C348A762DE96A3CA6AAFC89
SHA256
9077E6ED38B77E142C65AD4125717A7630D90FC402F0CDFBC7FBF95660C21016
...
PS F:\ignite-wal\V_HP_LK_DCN01> ls
ModeLastWriteTime Length Name
- --
-a--- 6/15/2018 2:21 PM 67108864 .wal
-a--- 6/15/2018 3:27 PM 67108864 0001.wal
-a--- 6/15/2018 3:44 PM 67108864 0002.wal
...
AFTER
PS F:\ignite-wal\V_HP_LK_DCN01> get-filehash .\*
Algorithm Hash
-
SHA256
B7CA93C0FEEE94CD60C468F615E2C16B009DF13AD3F799DAC5A8CAB1A6E3438D
SHA256
E3290E24F2C7F9967A6FD800466ECE6382BBC969274C6C1B49A1119C2B3ECE29
SHA256
9077E6ED38B77E142C65AD4125717A7630D90FC402F0CDFBC7FBF95660C21016
...
PS F:\ignite-wal\V_HP_LK_DCN01> ls
ModeLastWriteTime Length Name
- --
-a--- 6/15/2018 2:21 PM 67108864 .wal
-a--- 6/15/2018 3:27 PM 67108864 0001.wal
-a--- 6/15/2018 3:44 PM 67108864 0002.wal
...
On Wed, Jun 20, 2018 at 1:12 PM, dkarachentsev
wrote:
> 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/
>