You need to handle this within your code logic. The problem is, when a 500 Error is given back, you don't know what actually happened on the server side. For all you know, it could have been half way through its task.
You need to add logic within the client side and server side code, to handle any events like this. On Thu, Mar 24, 2011 at 6:29 AM, Shamail Tayyab <pleoma...@gmail.com> wrote: > Hi, > > We have a setup in which we can't afford downtime (even while > deployment). > > Our setup is based on lighttpd + django (on fcgi via flup). What my > problem is, when we restart django, the site goes down for about a > couple of seconds (and all API calls to DB remains incomplete > resulting in 500.html being rendered for users). > > We need a setup in which we can restart our system in a safe way. > > As an initial thought, instead of 1 site instance, lets have 2, then > use lighty's load balancing to have both the instances run, then drop > the previous instance. > > Is this feasible? Will it lead to inconsistencies? How can I still > ensure that calls on previous instance completely stops before > dropping it? > > Any other way to do this? > > > Tx > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
