Hi, If the issue is that the node is starting with a new persistent storage each time there could some issue with file system.
The algorithm to choose a persistent folder is 1) If IgniteConfiguration.consistentId is specified, use the folder of that name 2) Otherwise, check if there are any existing folders not locked by other nodes; if one is found, use that 3) Otherwise, generate a new consistentId and create a new folder for it I assume that when Ignite checks your folders on step 2 they appear to be locked even though they are not. Perhaps the file system doesn’t unlock them fast enough, or something similar happens. Look for messages like “Unable to acquire lock to file” at the start of the nodes to see if that’s the case. Try to specify consistentId explicitly – perhaps it’ll solve the issue. Thanks, Stan From: abatra Sent: 1 октября 2018 г. 11:47 To: [email protected] Subject: Re: Is ID generator split brain compliant? I believe it won't work either. I will try it soon and share the result. Could you please share some pointers that I should look at for debugging persistence? I have org.apache.ignite=DEBUG in logs and IGNITE_QUITE set to false. There a lot of logs, most of which I can not make sense of w.r.t. persistence. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
