ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: Native persistence Cache data not loading when restart the server node
Date Tue, 27 Feb 2018 17:57:34 GMT

Ignite supposes there is another node up and running, which locks file

This protects new Inite node from using same DB folder concurrently with
other running node.

Is previous node process alive?

When previous process will be shut down, next restart will use 'node00'
folder with data.

Dmitriy Pavlov

вт, 27 февр. 2018 г. в 20:47, siva <siva.karna@bizruntime.com>:

> Hi,
> We are using Ignite Native persistence with one server node and one client
> node
> Due to network problem system shutdown ,when we are trying to start the
> ignite,its creating new persistent storage folder under work/db,so whatever
> the data under old persistent storage folder ,its not loading to the cache
> .When we check the log file ,we found that "2018-02-27 17:43:11 INFO
> PdsFoldersResolver:475 - *Unable to acquire lock to file
> [/home/apache-ignite-fabric-2.3.0-bin/work/db/node00-17cba8d3-43b3-4e43-8546-d52ec3b20f02],
> reason: null".*
> Can you guys help us how to resolve this issue and get data into cache.Our
> all application data is in that node only. I have attached the screen
> shots.**
> <http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Capture.png>
> <http://apache-ignite-users.70518.x6.nabble.com/file/t1379/cachedata.png>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

View raw message