[OVSDB-292] Clustering: DataStoreUnavailableException when shard leader is killed Created: 08/Feb/16 Updated: 02/Feb/17 Resolved: 02/Feb/17 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Clustering |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Vishnoi | Assignee: | ranjithkumar_t |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5274 |
| Priority: | Normal |
| Description |
|
Southbound plugin throws DataStoreUnavailableException while read transaction when shard leader node is killed. This only happens when shard leader node is killed rather then shutting it down gracefully. |
| Comments |
| Comment by Anil Vishnoi [ 09/Feb/16 ] |
|
Lowering the priority, i am not able to recreate this issue. |
| Comment by ranjithkumar_t [ 07/Apr/16 ] |
|
Hi Anil, For recreating the bug the following steps are followed 1. Cloned OVSDB project and switched to stable/beryllium branch. The following virtual machines are used to create OVSDB 3 node clustering 10.0.0.1, 10.0.0.2, 10.0.0.3 Observation : 1 ( Down Leader node 10.0.0.1) – One Node Failure 1. Leader node is 10.0.0.1 the remaining two nodes are followers. Observation : 2 ( Down Leader node 10.0.0.2) – Two Node Failure 1. Now the Leader node is 10.0.0.2 and the remaining one node is follower. http://10.0.0.3:8181/restconf/operational/network-topology:network-topology/ org.opendaylight.controller.md.sal.common.api.data.DataStoreUnavailableException: Shard member-3-shard-topology-operational currently has no leader. Try again later. at org.opendaylight.controller.cluster.datastore.NoOpTransactionContext.executeRead(NoOpTransactionContext.java:67) ... 23 more Caused by: org.opendaylight.controller.cluster.datastore.exceptions.NoShardLeaderException: Shard member-3-shard-topology-operational currently has no leader. Try again later. at org.opendaylight.controller.cluster.datastore.ShardManager.createNoShardLeaderException(ShardManager.java:744) at org.opendaylight.controller.cluster.datastore.ShardManager.onShardNotInitializedTimeout(ShardManager.java:551) I am not sure the singleton cluster is supported in 3 node OVSDB clustering mode. |
| Comment by Jamo Luhrsen [ 03/May/16 ] |
|
I have tried to reproduce this with Beryllium SR2 candidate distro [0].
I tried this several times, and never saw the DataStoreUnavailableException. I did see many of 2016-05-03 17:43:56,597 | INFO | ult-dispatcher-5 | ShardManager | 185 - org.opendaylight.controller.sal-d |
| Comment by Anil Vishnoi [ 02/Feb/17 ] |
|
Looks like this issue is not recreatable. Please re-open the issue if you are able to recreate it. |