[CONTROLLER-1953] Cluster ends up with a leader=null state when running a daexim export on non-leader Created: 06/Jul/20  Updated: 02/Jul/21  Resolved: 02/Jul/21

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

Type: Bug Priority: Medium
Reporter: Tejas Nevrekar Assignee: Oleksii Mozghovyi
Resolution: Cannot Reproduce Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

As demonstrated,
1. Brought down the ODL6(non-voting node)
2. Change the default-config leader
3. Ran down-unreachable-nodes
4. Started the ODL6 and monitored the ​leaderId=null messages and ODL6 managed to come up clean.

On leader node ODL1 for default-config

2020-06-22T21:33:03,046 | INFO | opendaylight-cluster-data-shard-dispatcher-41 | Shard | 290 - org.opendaylight.controller.sal-clustering-commons - 1.9.1 | member-1-shard-inventory-config (Follower): Follower is out-of-sync so sending negative reply: AppendEntriesReply [term=15, success=false, followerId=member-1-shard-inventory-config, logLastIndex=6, logLastTerm=7, forceInstallSnapshot=false, needsLeaderAddress=false, payloadVersion=9, raftVersion=4, recipientRaftVersion=3]

​On non-voting ODL6 node,

2020-06-22T21:33:17,862 | INFO | opendaylight-cluster-data-shard-dispatcher-37 | ShardManager | 298 - org.opendaylight.controller.sal-distributed-datastore - 1.9.1 | shard-manager-config: Received LeaderStateChanged message: LeaderStateChanged [memberId=member-6-shard-topology-config, leaderId=null, leaderPayloadVersion=9]
2020-06-22T21:33:17,872 | INFO | opendaylight-cluster-data-shard-dispatcher-37 | ShardManager | 298 - org.opendaylight.controller.sal-distributed-datastore - 1.9.1 | shard-manager-operational: Received LeaderStateChanged message: LeaderStateChanged [memberId=member-6-shard-entity-ownership-operational, leaderId=null, leaderPayloadVersion=9]
​

 Comments   
Comment by Oleksii Mozghovyi [ 27/May/21 ]

I couldn't reproduce this issue, and it seems like daexim export is not the root cause of the problems described here. If there is no additional input, I'm afraid we can only close this issue.

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