You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Yakov Zhdanov <yz...@apache.org> on 2017/09/15 13:48:13 UTC
Re: Ignite cluster with persistent store enabled did not load from
wal after restarting.
Guys, it seems that we have the same issue that was described in thread -
Specifying location of persistent storage location
I filed a ticket some time ago -
https://issues.apache.org/jira/browse/IGNITE-6285, Alex G, can you take a
look if this ticket makes sense?
--Yakov
Re: Ignite cluster with persistent store enabled did not load from
wal after restarting.
Posted by Alexey Kukushkin <ku...@gmail.com>.
Ray,
Yakov just pointed me to this thread
<http://apache-ignite-users.70518.x6.nabble.com/Specifying-location-of-persistent-storage-location-tc16636.html>
where
user had a problem with IP address changing between the cluster restarts.
The persistent data directories inside work/db have names built as a
concatenation of local IP addresses and ports. Thus, if your node receives
a different IP address between the restarts, you will not have your
persistent data since the node will initialise from a different persistent
data file. You would need to bind your discovery SPI to specific address to
work around that. There is an issue opened to properly fix it.
Please also consider that as a potential cause.
Re: Ignite cluster with persistent store enabled did not load from
wal after restarting.
Posted by Alexey Kukushkin <ku...@gmail.com>.
Ray,
Yakov just pointed me to this thread
<http://apache-ignite-users.70518.x6.nabble.com/Specifying-location-of-persistent-storage-location-tc16636.html>
where
user had a problem with IP address changing between the cluster restarts.
The persistent data directories inside work/db have names built as a
concatenation of local IP addresses and ports. Thus, if your node receives
a different IP address between the restarts, you will not have your
persistent data since the node will initialise from a different persistent
data file. You would need to bind your discovery SPI to specific address to
work around that. There is an issue opened to properly fix it.
Please also consider that as a potential cause.