Lars Hesel Christensen

ok, I think this might make sense to me - it is very likely related to the errors in the log. We've just changed the cluster com to be truly...

ok, thanks for the info! We'll have to think of a better way to handle when the outgoing data blocks the socket.

That makes sense, the next commit is the one where we re-implemented the cluster cross node publication logic. And great you have this workaround for now... will keep you posted.

Reopening this so we don't loose it from the radar

Sure - I'll try. This is all in the context of VerneMQ and MQTT over websockets. Often we can set some pre-defined (small) values for the sndbuf and recbuf sizes...

We worked around this by implementing a `stream_handler` and `cowboy_sub_protocol` (which you kindly suggested when we first discussed it on IRC) which inserts the socket into our websocket state -...

Hi, so since subscriptions are part of the eventually consistent metadata it is expected that subscriptions are not atomic/instant throughout the cluster. Usually the propagation is almost instant or at...

Transferred this to the `vernemq-docker` repo. Looking at the stack trace my guess is that the node comes with a new node name but with the old metadata - so...

Hi @bcardarella is this something you'd consider adding or can I help this along in some way? I'm having the same issue that the IdP I'm using currently only supports...

I like this idea a lot! I'll assign this to the 1.7.0 milestone for now.