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
I've been perusing this code and working on a memberlist-compliant service in another language for kicks. The README.md and config.go seem to suggest that with the right configuration TCP will not be used at all.
Unfortunately, as @tonglil described above: TCP is used when one issues a memberlist.Join as it calls pushPullNode which in turn calls sendAndReceiveStatehere.
Should sendAndReceiveState support UDP at the expense of bandwidth?
Hi @tonglil and @jpfuentes2 this has been in there for quite a long time - a43fd04#diff-c5a0fd3b9b3c075b837e5f6dc71db15d. We will have to think through the implications of omitting this step - I'm not 100% sure if things would converge correctly without this on the initial join without going through the details.
Configuration:
I am trying to minimize or eliminate TCP connections between nodes.
However when I start the server, it still creates TCP connections.
Does memberlist always sync state when it is joining a cluster?
The text was updated successfully, but these errors were encountered: