[CONTROLLER-782] Clustering : Applying a recovered journal to Shard does not happen during recovery Created: 07/Sep/14  Updated: 11/Sep/14  Resolved: 11/Sep/14

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

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

Operating System: Mac OS
Platform: PC


External issue ID: 1734

 Description   

The RaftActor does not immediately apply state during recovery and instead relies on state changes or replication to apply the state. This can lead to a couple of issues. Firstly in a single node cluster the Leader will not reconstruct it's state till it gets the very first new transaction post recovery. Secondly this can lead to really slow application of the very first new transaction if the recovery process involves a lot of operations.

To reproduce the first problem do the following,

1. Start a single node cluster
2. Connect mininet to the cluster and create a small topology
3. Kill the controller (kill -9)
4. Exit mininet
5. Start the controller
6. Using restconf check if the nodes that were previously added are present

In this scenario the nodes should be present



 Comments   
Comment by Moiz Raja [ 11/Sep/14 ]

https://git.opendaylight.org/gerrit/#/c/10890/

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