These are chat archives for fanout/pushpin

23rd
Nov 2018
Jorge S. Cuesta
@jorgecuesta
Nov 23 2018 02:18
@jkarneges I was doing a little test and found that if I change the timeout from 30 (copied from example on pushpin website - c:{"type": "keep-alive", "content": "{}", "timeout": 30} https://pushpin.org/docs/advanced/#keep-alives it close my websocket connection, but if I leave it on 30 it work nice, I wish to increase that value to prevent a lot of messages of keep alive.
have you some idea or trick to solve that?
note: I’m using fanout/pushpin:latest in docker
Justin Karneges
@jkarneges
Nov 23 2018 17:30
@jorgecuesta other values for timeout work for me (e.g. 60). what do you mean your websocket gets closed if the value is other than 30? closes instantly if other values used, or still times out?
Jorge S. Cuesta
@jorgecuesta
Nov 23 2018 17:31
@jkarneges on pushpin logs it say something about ws-control and after that control it say that ws is unavailable and sent close message
Jorge S. Cuesta
@jorgecuesta
Nov 23 2018 17:38
when I set from 30 to 45 it work right, and that ws-control don’t say that ws is unavailable.
I wish to set something like 2 minutes or more to prevent an overload on pushpin with a lot of connections
and in my client I sent something like 5 minutes, to be sure that pushpin has enough time to sent a keep-alive content.
Justin Karneges
@jkarneges
Nov 23 2018 20:01
120 seconds works fine for me. it could be that there's a shorter timeout somewhere between your client and pushpin, e.g. in your LB or routers
Jorge S. Cuesta
@jorgecuesta
Nov 23 2018 20:34
I just use Kong, I should set something there? (if you know of course)