You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by Mikael <mi...@telia.com> on 2018/06/11 08:21:52 UTC

"WAL segment tail is reached", Is it a problem ?

Hi!

I often get this warning when I start my Ignite server node:

WAL segment tail is reached. [ Expected next state: 
{Index=46,Offset=9882876}, Actual state : {Index=17324643,Offset=0} ]

Native persistence enabled, am I doing anything wrong, the application 
and Ignite is shutdown correct and I still get this ?

Mikael

Re: "WAL segment tail is reached", Is it a problem ?

Posted by Mikael <mi...@telia.com>.

I have turned on full logging and I will include that next time it happens.

Mikael


Den 2018-06-11 kl. 17:26, skrev dkarachentsev:
> Hi Mikael,
>
> Please share your Ignite settings and logs.
>
> Thanks!
> -Dmitry
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>

Re: "WAL segment tail is reached", Is it a problem ?

Posted by dkarachentsev <dk...@gridgain.com>.

Hi Mikael!

Don't worry about this message and you may just ignore it. It's absolutely
OK and means that WAL was read fully. The question is why it's WARNING... In
future releases it would be changed to INFO and message content to avoid
such confusing.

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: "WAL segment tail is reached", Is it a problem ?

Posted by Mikael <mi...@telia.com>.

Hi!

Ok, lets see if this helps, here is a log from when it happens with 
"debug" enabled, it's just at the end of ignite.log file included and 
looks like:

09:22:08 [main] INFO : Read checkpoint status 
[startMarker=c:\slask\usfnew\ignite\persistence\node00-aa432e75-26ac-4af4-b631-d8944f8e155d\cp\1528787179283-4876401a-d2e8-4a90-972e-8e88115ba586-START.bin, 
endMarker=c:\slask\usfnew\ignite\persistence\node00-aa432e75-26ac-4af4-b631-d8944f8e155d\cp\1528787020090-4ee11808-263a-4955-bbea-2828f7e65af1-END.bin]
09:22:08 [main] INFO : Started page memory [memoryAllocated=100,0 MiB, 
pages=24808, tableSize=1,9 MiB, checkpointBuffer=100,0 MiB]
09:22:08 [main] INFO : Checking memory state 
[lastValidPos=FileWALPointer [idx=55, fileOff=17480259, len=75832], 
lastMarked=FileWALPointer [idx=55, fileOff=61695692, len=342535], 
lastCheckpointId=4876401a-d2e8-4a90-972e-8e88115ba586]
09:22:08 [main] WARN : Ignite node stopped in the middle of checkpoint. 
Will restore memory state and finish checkpoint on node start.
09:22:08 [main] DEBUG: Initialized WAL cursor [start=FileWALPointer 
[idx=55, fileOff=17480259, len=75832], end=null, curWalSegmIdx=54]
09:22:08 [main] DEBUG: Reserved work segment [absIdx=55, pins=1]
09:22:08 [main] DEBUG: Reading next file [absIdx=55, 
file=c:\slask\usfnew\ignite\wal\node00-aa432e75-26ac-4af4-b631-d8944f8e155d\0000000000000005.wal]
09:22:08 [main] WARN : WAL segment tail is reached. [ Expected next 
state: {Index=55,Offset=62038227}, Actual state : 
{Index=795584623626172805,Offset=13791} ]

The ignite configuration is also included (the caches are created from 
the application in Java but it's just a number of partitioned caches 
with backups=0 with native persistence, I am just running this on a 
single node at the moment, the node was shutdown nice and friendly and 
it's running in FSYNC mode, it does not happen every time the node is 
started, maybe every 5 or 6 times or so.

Mikael


Den 2018-06-11 kl. 17:26, skrev dkarachentsev:
> Hi Mikael,
>
> Please share your Ignite settings and logs.
>
> Thanks!
> -Dmitry
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>

Re: "WAL segment tail is reached", Is it a problem ?

Posted by dkarachentsev <dk...@gridgain.com>.

Hi Mikael,

Please share your Ignite settings and logs.

Thanks!
-Dmitry



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/