Slow operations should be non-blocking #4

Activity

1. brummett commented on Aug 8, 2014

   

   brummett

   on Aug 8, 2014

   ContributorAuthor

   More actions

   uploading a template file
2. brummett commented on Nov 11, 2014

   

   brummett

   on Nov 11, 2014

   ContributorAuthor

   More actions

   The only possible slow thing now can be creating a DB from a template or a template from a DB
3. nnutter commented on Feb 28, 2015

   

   nnutter

   on Feb 28, 2015

   Contributor

   More actions

   I'm wondering if create the DB from the template has some Postgres lock contention, see genome/genome#524, which is causing HTTP timeouts.
4. nnutter

   added

   bug

   on Feb 28, 2015
5. nnutter commented on Mar 1, 2015

   

   nnutter

   on Mar 1, 2015

   Contributor

   More actions

   I increased the timeouts to 30 seconds in genome-env and now I saw 4 out of ~12 model tests get this error:

   Got error response 502: Proxy Error at /usr/bin/test-db-database-create line 15
6. brummett commented on Mar 2, 2015

   

   brummett

   on Mar 2, 2015

   ContributorAuthor

   More actions

   The original purpose of this issue was to start using the Mojo event loop in places where long-running handlers (like the old dump-database-load to copy DBs) would block the system from servicing other HTTP requests.

   The docs for Mojo::Pg shows how this might work. Look for Mojo::IOLoop->delay.

   Do you know if the timeouts we're getting are because it's taking too long to service a new HTTP connection (because it's still busy doing the last one) or to copy the database? The first problem would be fixed with this event loop thing, but not the second.