usegalaxy.org uses a five host setup:
Web requests are balanced only with a DNS round-robin (i.e. there are two A records for usegalaxy.org), which is not ideal since it does not do any load balancing or health checks. A better setup would include a 6th host with nginx proxying the web hosts.
Two commonly used [Galaxy][galaxy] server configurations are the use of [uWSGI Zerg Mode][uwsgi-zerg-mode] and [uWSGI Mules][uwsgi-mules] as [Galaxy job handlers][galaxy-scaling]. These features are not easily compatible because Galaxy job handlers rely heavily on having unique server names, and handlers' server names must be persistent across restarts. Because zerg mode results in running two Galaxy servers simultaneously (however briefly), using mules with zerg mode would necessarily mean running mules with overlapping server names.
In a typical Galaxy zerg mode setup, the newly started zergling (B) terminates the old zergling (A) once B is ready to serve requests. Zergling B then continues to serve requests until another zergling (C) is started and terminates B.
It is possible to get both zerg mode and mules working together by configuring zergling B to start without mules, and perform a double zerg dance on each restart:
| Adding a new disk to a bhyve vm takes a few steps. | |
| 1. increase the quota on the zfs dataset to accomodate the additional | |
| space. | |
| 2. create a zvol inside the zone | |
| 3. stop the vm and update its configuration to reflect the change | |
| 4. start the vm, login and use the disk | |
| # update quota |
| galaxy_main=> EXPLAIN ANALYZE SELECT job.id AS job_id, | |
| job.create_time AS job_create_time, | |
| job.update_time AS job_update_time, | |
| job.history_id AS job_history_id, | |
| job.library_folder_id AS job_library_folder_id, | |
| job.tool_id AS job_tool_id, | |
| job.tool_version AS job_tool_version, | |
| job.state AS job_state, | |
| job.info AS job_info, | |
| job.command_line AS job_command_line, |
This gist has been superceded by https://github.com/galaxyproject/usegalaxy-playbook/wiki
Make sure nobody is running a docker container before restarting the service...
$ ssh g2test@cvmfs0-tacc0.galaxyproject.org