-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues while electing leader on a single node quorum cluster. #931
Comments
Hi @navdeep-kaur - I checked in 2.4.0 version bringing up a single node cluster and it works fine for me.
Can you please check if the |
@vsmk98 we have entries for all nodes (that will be added ) in the quorum network in the static-nodes.json when we start the network with a single node. This used to work in v2.2.3. Has something changed around this? |
@vsmk98 this used to work in v2.2.3, has something updated in v2.4.0 |
@MrHmP, @navdeep-kaur , there is no change in the raft consensus behaviour between In 2.4.0 as a part of the API response we also wanted to return the role of the node in the network. Because of this if there is no leader in the network, the api returns an error. For your scenario, my suggestion will be to
Please let me know if this is workable for your scenario. |
I am closing this issue. Please re-open if necessary. |
I don't understand why it doesn't work with the new version if it was working for older version. Sure we have a different way of provisioning our network now, but we have to change our code for cluster deployment. |
@Himanshu-Pandey, at I mentioned, at network level it was not working with one node in |
@Himanshu-Pandey thanks for your feedback. @vsmk98 is working on resolving this. The api will not return an error going forward, but it will return the cluster details with a nil for the role until a leader is elected. |
@Himanshu-Pandey I have created the PR to resolve this. Please refer to raft api documentation page https://github.com/jpmorganchase/quorum/blob/fix/raft-cluster-api/docs/Consensus/raft/raft-rpc-api.md for details of the |
Thanks @vsmk98 |
Closing this issue as the PR is merged. |
Hi there,
On upgrading to quorum 2.4, when we are starting up the cluster with a single node, the raft_cluster is responding with {"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"no leader is currently elected"}}. The single node is unable to elect itself as the leader and is always chosen as a candidate instead.
Expected behaviour
The single node should be elected as the leader.
The idea is to spin up a single boot node and run add peer for all the other nodes that we want to add to the quorum network.
The text was updated successfully, but these errors were encountered: