> Hi there, > > We've been having a problem recently where it appears that the uWSGI > Emperor is restarting all vassals -- or, perhaps is restarting itself. > > Our setup is that on a given web server, all Python code for the running > vassals is mounted over NFS. Sometimes there are glitches on the NFS > server, so it stops responding for a minute or so. When it comes back, > all vassals appear to restart; this puts so much load on the machine > that it's essentially non-responsive for some time. So what would be an > outage lasting a couple of minutes (bad) can take up to 20 minutes to > clear (very, very bad). > > Vassals are all configured via .ini files in a specific directory, so it > appears that either: > > * The emperor is restarting all of its vassals, or > * The emperor is restarting itself, which means it's shutting down all > of the existing vassals as it exits, then reading all of the vassal > files on startup. > > Is there something in the emperor that makes it restart either all > vassals or itself when a subset of the vassals stop responding for some > time? > > > All the best, > > Giles > >
Hi Giles, do you have emperor logs during the NFS outage ? Are the vassals files physically in the nfs storage ? How you mounted the nfs filesystem ? (i mean the options, like sync, intr and so on) -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
