Hi!
I got a few of them before with 2.5, have not seen any yet with 2.6, it
was actually a warning before but was changed to info, I was told it's
not a problem and nothing to worry about, as far as I can tell no data
was ever lost.
Mikael
Den 2018-10-03 kl. 21:48, skrev Raymond Wilson:
We see instances of the below error appearing in our logs (using
Ignite.Net v2.6 with persistent storage) on server node startup:
2018-10-04 08:38:24:0079 2827983 2018-10-04
08:38:24,046 [1] INFO MutableCacheComputeServer. Stopping WAL
iteration due to an exception: Failed to read WAL record at position:
31062042, ptr=FileWALPointer [idx=33, fileOff=31062042, len=0]
The type of the log message is INFO, but it appears to indicate an
issue with the WAL files in our persistent store. All our data regions
are configured with WalMode = Fsync, so I’m a little surprised to be
seeing what looks like WAL integrity errors.
The next message in the log is this, which indicates Ignite was not
affected:
2018-10-04 08:39:02,116 [6] INFO MutableCacheComputeServer. Resuming
logging to WAL segment [file=[… very long path…]\0000000000000003.wal,
offset=31062042, ver=2]
A few lines later there is a repeat of the initial exception related
message:
2018-10-04 08:39:03,142 [6] INFO MutableCacheComputeServer. Stopping
WAL iteration due to an exception: Failed to read WAL record at
position: 31190597, ptr=FileWALPointer [idx=33, fileOff=31190597, len=0]
Then this line appears:
2018-10-04 08:39:03,813 [6] INFO MutableCacheComputeServer. Finished
applying WAL changes [updatesApplied=146, time=1272ms]
The node appears to initialize correctly after this logging.
Does anyone else see this behaviour? Is it something to be concerned
about or normal logging to be expected after termination of running
server instances?
The
Thanks,
Raymond.
