-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Introduce a way to easily check cluster status #2503
Comments
Ref #2275: I don't completely support throwing exception because we don't do that even from Jedis class. Throwing exception from JedisCluster constructor seems contradictory to me. |
This issue is marked stale. It will be closed in 30 days if it is not updated. |
Closing this issue in favor of these options. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
There should be a easy to check if the cluster is initialized properly. I.e. if there is a pool initialized for each hash slot.
For example, if we add a
isInitialized()
, users would at least be able to doActual behavior
Currently it can be done by
getClusterNodes()
, may be combining with a command, like PING. But we should introduce a easier way.The text was updated successfully, but these errors were encountered: