[CONTROLLER-804] Clustering : Restarting a controller node in a 3 node cluster causes it to not be able to find the leader Created: 11/Sep/14 Updated: 16/Sep/14 Resolved: 16/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: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1803 |
| Priority: | High |
| Description |
|
For steps checkout the clustering disaster recovery scripts in the integration repo. https://git.opendaylight.org/gerrit/#/c/11021/ |
| Comments |
| Comment by Moiz Raja [ 11/Sep/14 ] |
|
2014-09-11 02:59:09,916 | WARN | lt-dispatcher-18 | ShardManager | 152 - com.typesafe.akka.slf4j - 2.3.4 | akka://opendaylight-cluster-data/user/shardmanager-config | Supervisor Strategy of resume applied |
| Comment by Moiz Raja [ 16/Sep/14 ] |
|
This happens to be an issue with configuration. The issue was kind of like this. Let's say you have 3 nodes and node 1 was setup to be the only seed node. Now you bring down the seed node and bring it back up. When the leader node comes back up it tries to join cluster however the cluster has changed because a new leader was elected. The fix for this is one of the following, a. When the leader is restarted set the seed node for it as one of the existing nodes in the cluster (the one that is running) |