-
Notifications
You must be signed in to change notification settings - Fork 23.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
"cluster nodes" serialization format change / documentation #4186
Comments
Sorry @mgravell! I totally forgot to mention this in the release note, section of backward incompatible changes. Unfortunately compatibility with Docker / NAT-ted environments forced changes in the Cluster bus binary protocol, and also needed the ability to have arbitrary bus TCP port, it is no longer mandatory to be at +10000 offset. So now also the cluster bus port is announced after the "@". There are no other changes AFAIK. |
In practical terms this means that you can ignore the |
That's what I assumed; I've pushed an updated build of my client lib, but note that this could also adversely affect other clients that use |
Thanks, I'll send a note via ML / Twitter and update the 4.0 changelog accordingly. |
Testing against 4.0.1 configured as a cluster using the basic 6-node config in the tutorial; example output of
cluster nodes
:This does not match the documentation - see the
127.0.0.1:7003@17003
for example. What was<ip:port>
is now<ip:port@something>
Request clarification.
Side note: yes, I should move to
cluster slots
, but:cluster slots
didn't exist when I wrote this part of the library code :)Environment in case this matters: WSL (Windows 10) running Ubuntu 16.04.2 LTS
The text was updated successfully, but these errors were encountered: