[PERSISTENC-7] akka persistence with ignite cluster db - instance data is not available for RESTCONF read access Created: 04/Dec/20  Updated: 02/Feb/22

Status: Open
Project: persistence
Component/s: None
Affects Version/s: None
Fix Version/s: unspecified

Type: Bug Priority: High
Reporter: Suresh PERUMAL Assignee: Suresh PERUMAL
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hi,

 

We have migrated leveldb with ignite / cassandra and single node it is working fine.

We have created a ignite / cassandra cluster between two ODL standalone instances . Data is getting replicated between these two nodes. Like Node1, Node2.

1. Node-1 is Active, node-2 is passive. Node-1

2. All the write operations were done in Node-1

3. Node-2 has all the data replicated

4. RESTCONF from Node-1, we are able to read the data, 

5. RESTCONF from Node -2 shows below error

 
{"errors":{"error":[

{"error-type":"application","error-tag":"data-missing","error-message":"Request could not be completed because the relevant data model content does not exist "}

]}}
We would like how to reload node-2's in-memory journal in MDSAL In memory data store?

 

 Comments   
Comment by Suresh PERUMAL [ 04/Dec/20 ]

Hi Robert, I need your support to fix the data replication via using ignite/cassandra cluster and bring the journal messages to get replayed by persitent actor automatically on the other node. 

Let me know

Comment by Robert Varga [ 08/Dec/21 ]

pasavy sorry, this got lost in my mailbox.

Do I understand your setup as using Ignite/Cassandra as the Akka persistence with the distributed data store?

Generated at Wed Feb 07 20:36:46 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.