[OVSDB-247] Singleton Cluster is not happened Created: 08/Jan/16  Updated: 02/Feb/16  Resolved: 02/Feb/16

Status: Resolved
Project: ovsdb
Component/s: Southbound.Open_vSwitch
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: ranjithkumar_t Assignee: Anil Vishnoi
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File akka.conf    
External issue ID: 4904

 Description   

Observation-1 :

In 3 node clsuter, If all nodes goes down and then restarted node(10.106.138.107) which node act as a leader when nodes are up. now achieved singleton cluster. the leader will be selected and this node act as singleton cluster

http://10.106.138.107:8181/jolokia/read/akka:type=Cluster

{"timestamp":1452166117,"status":200,"request":

{"mbean":"akka:type=Cluster","type":"read"}

,"value":{"Available":true,"ClusterStatus":"{\n \"self-address\": \"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550\",\n \"members\": [\n

{\n \"address\": \"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550\",\n \"status\": \"Up\"\n }

\n ],\n \"unreachable\": [\n \n ]\n}\n","Unreachable":"","Members":"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550","Leader":"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.107:2550","MemberStatus":"Up","Singleton":true}}

Observation-2 :

All 3 nodes goes down and then restarted any one of the non-leader node (10.106.138.251 and 10.106.138.111), leader will not be elected and not achieved singleton cluster.

http://10.106.138.251:8181/jolokia/read/akka:type=Cluster

{"timestamp":1452182366,"status":200,"request":

{"mbean":"akka:type=Cluster","type":"read"}

,"value":{"Available":false,"ClusterStatus":"

{\n \"self-address\": \"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.251:2550\",\n \"members\": [\n \n ],\n \"unreachable\": [\n \n ]\n}

\n","Unreachable":"","Members":"","Leader":"","MemberStatus":"Removed","Singleton":false}}

http://10.106.138.111:8181/jolokia/read/akka:type=Cluster

{"timestamp":1452165274,"status":200,"request":

{"mbean":"akka:type=Cluster","type":"read"}

,"value":{"Available":false,"ClusterStatus":"

{\n \"self-address\": \"akka.tcp:\/\/opendaylight-cluster-data@10.106.138.111:2550\",\n \"members\": [\n \n ],\n \"unreachable\": [\n \n ]\n}

\n","Unreachable":"","Members":"","Leader":"","MemberStatus":"Removed","Singleton":false}}

Many times I have tried but got above observations only.

Reproduce this issue, following below steps
1) 3-node is up
2) After election one node elected as a leader, then down all 3 nodes
3) Restart any one down node which is not act as a leader.

 Comments   
Comment by ranjithkumar_t [ 08/Jan/16 ]

Attachment akka.conf has been added with description: For your reference i have attached akka.conf file

Comment by Anil Vishnoi [ 09/Jan/16 ]

I don't think singleton cluster is supported, because RAFT won't work in case of single node and in clustering mode that single node will be pretty-much useless.

I would defer it to cluster experts, but that's my understanding.

Also this is not ovsdb bug and i would suggest you sent a mail to controller-dev mailing list and clarify the expected behavior in these scenario. If they says it's not expected behavior please open bug against controller project.

Thanks
Anil

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