Number of master nodes

[nordix]

Number of master nodes

[bjosv]

There is no API for getting this information, but it would be possible to get this kind of knowledge from the internals via the context. The risk of doing it is that the internals might change though..

The known master nodes could be inspected via an async cluster context, and the number of known master nodes would be:
dictSize(acc->cc->nodes).

To check which are active you would need to check the state of them (via a cluster_node's con or acon).

Replica information is only kept when configured to do so. It can be enabled via redisClusterSetOptionParseSlaves(..) and the replica node information is kept in its master cluster_node (see slaves in the struct cluster_node).
You would need to check the state of the replica-nodes in the same way as for the masters.

If you have ideas of an API we are happy to get a draft or even a proposal via a PR :)

[SS-TruMinds]

Thank you very much for the helpful information.

To elaborate further, we have the following requirements from our applications:

1. inform me when at least one connection is available
2. inform me when no connections are available

The first one is easy at least when we create the connection - we inform the application from the first connect callback. We also keep track of all the masters from which we receive all the connect callbacks.
Second part is a bit tricky as disconnect callbacks don't match against the connect callbacks. We can knock off the known masters on the basis of disconnect callbacks, but their slaves would now become masters so it's actually not a loss of master in a sense.

We will use the trick you mentioned above to inspect the state of known masters. Hopefully this gets updated based on the run-time state of the cluster?

Thank you again for all the help. Yes we will certainly look at the possibility of a PR once we have a better understanding.

[SS-TruMinds]

A follow-up on this issue.

We have noticed that the master nodes do not get updated dynamically.
eg. if Master1 process dies & Slave1 takes it's place in the cluster, the list of master nodes held inside the cluster context does not get updated.
As a result, if we lose the masters registered at the context creation time, we can no longer communication with the cluster even if it is still up.

Please advice if there is a way to update the masters depending on the runtime status of the cluster?

Thank you.