Can I make transaction writes to the persistence store atomic with write-behind? As you wrote, writes always happen on the primary node when write-behind is enabled. This means that if there were multiple keys modified in a single transaction and these keys belong to different primary nodes, the persistent store might get into an inconsistent state if any of the nodes fails to persist the change. Is that true?
My dataset is relatively small, about 16GB, so I can easily hold it in a single machine's RAM. I want to have a cluster of 2 nodes - master and slave for data safety and write-behind for performance. I require data consistency more than availability. I'm wondering if it's possible to configure Ignite to treat one node as the primary node for all map entries and the 2nd one for backups. Then only one node will be writing to the persistent store with write-behind enabled, so it'll always remain consistent. I was hoping that REPLICATED mode allows that, but it seems that it'll still distribute the entries over the 2 nodes. Do you have any ideas? As a bonus, I'd like to control which of the nodes holds the primary entries so I can embed all processing on that node in order to minimise the latency. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Persistent-CacheStore-and-backups-tp1368p1547.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
