Client connection checking

jamie commented

2017-05-24 06:03:23 +00:00

(Migrated from git.hazaar.io)

Due to an issue with haproxy in a live environment, where it would drop connections on the client side every minute causing the client to reconnect, but would not drop the server connection correctly, this is something that needs to be looked at.

Basically, if a connection is not dropped correctly it can sit there indefinitely. What we will need to do is periodically send a ping on connections to ensure they are still alive. This should cause the TCP layer to drop the connection if it is actually not active.

Due to an issue with haproxy in a live environment, where it would drop connections on the client side every minute causing the client to reconnect, but would not drop the server connection correctly, this is something that needs to be looked at. Basically, if a connection is not dropped correctly it can sit there indefinitely. What we will need to do is periodically send a ping on connections to ensure they are still alive. This should cause the TCP layer to drop the connection if it is actually not active.

jamie commented

2017-06-21 22:57:04 +00:00

(Migrated from git.hazaar.io)

added ~142 and removed ~135 labels

jamie commented

2017-08-14 23:40:42 +00:00

(Migrated from git.hazaar.io)

I can use the PING/PONG frames from the WebSocket specification: https://tools.ietf.org/html/rfc6455#section-5.5.2

jamie commented

2017-08-15 03:04:50 +00:00

(Migrated from git.hazaar.io)

closed via commit 255cbb250a

closed via commit 255cbb250ab1d5e930c71fe13da20c4c10ec5a95

jamie commented

2017-08-15 03:06:36 +00:00

(Migrated from git.hazaar.io)

mentioned in commit 255cbb250a

mentioned in commit 255cbb250ab1d5e930c71fe13da20c4c10ec5a95

Rows
Columns

Client connection checking #17