Hi,
We've got a HTTP client connecting to an active-passive cluster setup,
controlled through a traffic managed DNS entry and a good-to-go signal on
each cluster. When the good-to-go fails, the DNS switches to point at the
passive cluster. The client in question has no knowledge of whether a
failover has occurred, it's just hitting an endpoint on the traffic managed
address.
The client is resolving the DNS correctly and opening a TCP connection.
However, when the failover occurs, the TCP connection to the old cluster
stays active because of Go's persistent connections. The connection is not
idle (it still makes scheduled requests to the endpoint via its IP address)
and so is not closed when we close all idle connections.
Is there some way to set a maximum age for the TCP connection?
--
------------------------------
*This email was sent by a company owned by Financial Times Group Limited
("FT Group <http://aboutus.ft.com/corporate-information/#axzz3rajCSIAt>"),
registered office at Number One Southwark Bridge, London SE1 9HL.
Registered in England and Wales with company number 879531. This e-mail may
contain confidential information. If you are not the intended recipient,
please notify the sender immediately, delete all copies and do not
distribute it further. It could also contain personal views which are not
necessarily those of the FT Group. We may monitor outgoing or
incoming emails as permitted by law.*
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
