DocDVZ, Most probably you faced with the following issue https://issues.apache.org/jira/browse/IGNITE-8780. You can try to remove END file marker, in this case node will be recovered using WAL.
чт, 14 июн. 2018 г. в 12:00, DocDVZ <doc...@gmail.com>: > As i see, last checkpoint-end file, that invoked the problem, was created, > but not filled with data: > > > /opt/penguin/ignite/apache-ignite-fabric-2.5.0-bin/work/db/node00-203cc00d-0935-450d-acc9-d59cc3d2163d/cp$ > ls -lah > total 208K > drwxr-xr-x 2 penguin penguin 4.0K Jun 9 12:52 . > drwxr-xr-x 3 penguin root 4.0K Jun 9 14:27 .. > <...> > -rw-r--r-- 1 penguin penguin 16 Jun 9 12:49 > 1528537756580-node-started.bin > -rw-r--r-- 1 penguin penguin 0 Jun 9 12:52 > 1528537928225-a5e78b9c-26c8-4dc1-b554-2ee35f119f0a-END.bin > -rw-r--r-- 1 penguin penguin 16 Jun 9 12:52 > 1528537928225-a5e78b9c-26c8-4dc1-b554-2ee35f119f0a-START.bin > > what state does ignite checkpointing have in that moment? Is it save for > node persistent data to remove that empty file? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
