On Aug 25, 2012, at 10:07 PM, Kenneth R. Auerbach wrote:
Can someone tell me if stopping and then restarting the Galaxy process would prevent
currently-running jobs from completing after the restart? Will all the jobs remain in the
queue after the restart? Also, what is the best way to restart the Galaxy server? Users
are complaining that jobs are extremely slow to start running. Is there a way to speed
things up? Any info or suggestions would be greatly appreciated.
If you haven't taken some of the steps like using PostgreSQL instead of SQLite, and
setting 'set_metadata_externally = True', please do so, as these will make a big
difference on performance. Full documentation is at:
You can't restart the server and recover running jobs if they're running through
the local runner. Jobs that are waiting to run when the server shuts down will not be
lost. To recover running jobs, you'll need to set up one of the cluster job runners
(which you can do, even if you're only submitting jobs to the local system).
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at: