You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the external membership module it is possible to specify not only IPs but also URLs to bind to, and to disseminate. Would be good to be able to do the same in the core membership module. It should cover all the features of the external membership so as it could be used instead.
In core swim it is easier to support, because nodes are identified by UUID. It means each node can resolve its own URL to an IP, disseminate the IP, and periodically check if the URL has changed to a new IP. When it happens, it simply disseminates its new IP. The other members of the cluster will see the old and the new IP as one instance, because they have the same UUID, so it should work smoothly. IP change is even already supported.
Swim could re-resolve the URL, say, once per 5 seconds default, and expose it as an option.
The text was updated successfully, but these errors were encountered:
In the external membership module it is possible to specify not only IPs but also URLs to bind to, and to disseminate. Would be good to be able to do the same in the core membership module. It should cover all the features of the external membership so as it could be used instead.
In core swim it is easier to support, because nodes are identified by UUID. It means each node can resolve its own URL to an IP, disseminate the IP, and periodically check if the URL has changed to a new IP. When it happens, it simply disseminates its new IP. The other members of the cluster will see the old and the new IP as one instance, because they have the same UUID, so it should work smoothly. IP change is even already supported.
Swim could re-resolve the URL, say, once per 5 seconds default, and expose it as an option.
The text was updated successfully, but these errors were encountered: