On Friday, June 3, 2016 at 1:48:05 PM UTC+2, Cristiano Coelho wrote: > > El viernes, 3 de junio de 2016, 4:41:16 (UTC-3), Florian Apolloner > escribió: >> >> >> Yes, SIGTERM is a signal Python should handle nicely, SIGKILL will just >> nuke the process from earth and prevent any cleanup I think. Note that the >> OS will clean up though (sooner or later). As for the open connections: >> Check on postgres where from they are and then check on that machine to >> which process they belong and maybe use gdb to find out more. >> >> > > When I saw the issue the first thing I checked was the source IP and was > the amazon machine as expected, then I'm almost sure those connections were > used by the thread pools >
Don't be almost sure, investigate were that connection is coming from… > The only issue I see here on the postgres side would be that you have very >> long timeouts configured. >> > > Looks like postgres doesn't have any kind of connection timeout and you > need to use pg bouncer for that. > If the app died indeed, tcp keep alive should help. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ea3288a8-e67f-4319-9f67-d2e59cc342bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
