[CONTROLLER-963] Clustering : Use Normalized Node streaming code when persisting snapshots and replicating snapshots Created: 28/Oct/14  Updated: 25/Jul/23  Resolved: 04/Feb/15

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Moiz Raja Assignee: Tom Pantelis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
blocks CONTROLLER-962 Clustering : Utilize NormalizedNode s... Resolved
External issue ID: 2264

 Description   

Use NormalizedNode stream writer when,
1. Persisting a snapshot

  • The transaction that reads the data from the store should not serialize the NormalizedNode
  • CaptureSnapshotReply should pass the read NormalizedNode to the RaftActor wrapped by a Serializable. This will keep the interface generic.
  • To reduce memory issue the captured snapshot will not be stored in memory

2. Install snapshot

  • Change message to java serializable and rely on akka to write the serializable to the stream
  • When a snapshot needs to be installed the snapshot needs to be created.

 Comments   
Comment by Tom Pantelis [ 03/Feb/15 ]

Submitted https://git.opendaylight.org/gerrit/#/c/14620/

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