Since Galaxy need to be restarted sometime (load datatype, add ressources in 
.loc, apply changes in the galaxy.ini), is anybody of you have solutions to 
restart it without interrupt the service?

We are now using nginx, uwsgi and supervisord.

My hope is to split the Galaxy process in two group (1 uwsgi and 2 job handlers 
per group). That way, we will be able to restart the group1 and then the group2.

I was planning to set the 2 uwsgi servers and delegate the load balancing to 
ngnix (https://www.nginx.com/resources/admin-guide/load-balancer/ 
But maybe, some of you already implemented that and can provide me some advices 
or warnings.

The job handler part seems easier to deal with 

Thanks by advance


Gildas Le Corguillé - Bioinformatician/Bioanalyste

Plateform ABiMS (Analyses and Bioinformatics for Marine Science)
http://abims.sb-roscoff.fr <http://abims.sb-roscoff.fr/>

Member of the Workflow4Metabolomics project
http://workflow4metabolomics.org <http://workflow4metabolomics.org/>

Station Biologique de Roscoff - UPMC/CNRS - FR2424
Place Georges Teissier 29680 Roscoff FRANCE
tel: +33 2 98 29 23 81

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:

To search Galaxy mailing lists use the unified search at:

Reply via email to