Timeline for How to deal with TCP-sockets being dropped instead of closed server-side?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9 at 9:50 | comment | added | Buhb | @Hans-MartinMosner It is an actual situation, but I made up the numbers as an example. Like you've deduced, It doesn't affect service availability to any measurable degree in my specific case. However, I was hoping it was a problem that has a more satisfying solution that I could apply. | |
| Jan 9 at 9:48 | comment | added | Hans-Martin Mosner | <tongue-in-cheek>the first rule for problem solving is "have a problem" - if all you have is a broad idea of a scenario that may present a problem you don't have a problem</tongue-in-cheek> | |
| Jan 9 at 9:41 | comment | added | Buhb | @freakish Thanks for the feedback. I'm sure you can cherry-pick solutions and vendors to work around this problem. I asked the question because i have seen a rise in this "hey, your application just needs to deal with this" trend, and I'm trying to, ideally, learn that there are some best practices that I've just missed or, at least, learn that the loss in availability is acceptable for most scenarios, and that's the reason I can't find much written about it. | |
| Jan 9 at 9:10 | comment | added | freakish | @Buhb if you really need such reliability, then you need to move to infrastructure that doesn't have those problems. If big cloud providers don't suit you, then you need your own infrastructure. But honestly I don't think you've done your research properly. For example there are lots of real time mmo games, or real time video conferencing services running on cloud servers like AWS or GCP. | |
| Jan 9 at 9:10 | comment | added | Hans-Martin Mosner | This is not a good place to discuss possible scenarios. You didn't mention service migration and cloud before - is that the actual situation or just a possibility that you just thought of? How often is the service migrated? What are the normal response times? If a migration happens 1-2 times per day and causes a delay of a second for one client because you try 10 dead connections with a timeout of 100ms, who cares? | |
| Jan 9 at 8:33 | comment | added | Buhb | Thank you. If the pool uses, say, 10 connections, and you use it to call the other service 100 times per second, the keep-alive would have to be really frequent to be able to catch the problem in time. Also, the timeout would need to be very short, so this is unpractical (i've tried). When it comes to the "other service", lots of cloud infrastructure do cloud things where a service for instance migrates to another node and my experience is that this is done with zero respect for open sockets. | |
| Jan 9 at 8:08 | history | answered | Hans-Martin Mosner | CC BY-SA 4.0 |