https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1770 controller <p>3 nodes makes up a cluster,close one of the nodes,and deletes the snapshot and journal files on that node.CLOSE the node as soon as possible AFTER reboot it.Finally,reboot the node and some shard data of that node cannot be successfully synchronized from other nodes.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1770

Flower failed to synchronize data after it's snapshot synchronization failed

Bug Medium In Progress Unresolved Unassigned Guan Zhenhang Thu, 14 Sep 2017 12:04:39 +0000 Tue, 25 Jul 2023 08:24:46 +0000 clustering 0 3 <p>Cause Analysis:<br/> The persisted data has been removed after the first shutdown of the node,at this point,when the node is restarted,each shard of the node is in the initialization state because the local persistence content is empty,that is,the logIndex of each shard is -1(indicating that the shard has not been synchronized to any data).<br/> When the node is added to the cluster,the shard-leader on the other nodes synchronizes the data to the shard on the node through the raft protocol.Since shard-leader has done log compression, it is only possible to recover the data of the node via the snapshot message. At this point, the new startup node is closed, and it is possible that some of the shard's snapshot has not yet been completed.</p> <p>Resolvent:<br/> According to the above analysis, the status record of leader synchronization from snapshot to follower has no timeliness, which leads leader to judge snapshot synchronization with follower.The significance of this status record is to avoid sending snapshot messages repeatedly by leader.And the record is useless after the follower's shutdown,so the record cannot always be used as a basis for data synchronization between leader and follower.<br/> To this end,we have added a timeliness check to this status record,the record is invalid in ten minutes(according to our business data scale, ten minutes is a very conservative time interval),and leader will continue to synchronize data to follower.</p> <p>Our bug fix has passed 3 nodes test,we will push the code if someone can review.</p> <p>Adjust severity to match last status in bugzilla.</p> <p>Hi Guan,</p> <p>do you have a link to the patch for review? This is a blocker bug for our nitrogen release we are hoping to release in a week.<br/> The contributions are much appreciated.</p> <p>Why is this all of a sudden a blocker for SR1? It wasn't a blocker for nitrogen plus this is an edge case that has been there all along (no regression). </p> <p>I lowered the severity as I don't believe this needs to be a blocker.</p> Development External issue ID 9163 External issue URL Rank 0|i02smf: