Alta disponibilidad de Discourse

[jakimfett]

Has anyone played with a HAProxy/nginx/etc?

I could have sworn there was a how-to guide for a way to do distributed hosting, either via Docker or via multiple instances of Discourse all hitting a single high availability database server, but I can’t seem to find a guide for it.

Any thoughts? I’m currently serving a small single Discourse site, but am interested in learning as much as I can about scaling and load balancing of Discourse.

[jakimfett]

Found it, less than fifteen minutes after I posted. I’ll put any info on snags or clarifications that might be helpful into the conversation here.

[jakimfett]

The documentation is very fragmented. I’m going to attempt to pull it all together here.

Any chance I could get some input from @nx2zdk or @jspdng?

Use multiple Docker containers without exposing ports

This is an advanced setup. Don’t follow this unless you are experienced with Linux server administration and Docker. Hello everyone! If you don’t want to mess with the firewall rules and security of your server, you can configure your Docker multiple container setup with just links and no exposed ports! This way you can share your data container (postgres/redis) with other containers without exposing it to the internet. How to Edit your data.yml file commenting all the expose …

Linking containers for a multiple container setup

Multiple Container setup If you would like to connect web-only and data Discourse docker containers. There is optional setting for this, which is, you could specify a links key in container configuration (yaml file) to link those containers together ( i.e. linking web-only and data container ). This way is also known as Docker --link flag. Usage: If you are trying to link database container to your web container Add the following section in containers/web.yml links: - link: name:…

[jakimfett]

Info on avoiding port exposure:

Use multiple Docker containers without exposing ports

Just in case anybody stumbles here for running several Discourse instances behind https://github.com/jwilder/nginx-proxy: Set discourse to listen on a local link port and tell the proxy to use the container’s internal port 80 like expose: - "127.0.0.1:2836:80" env: VIRTUAL_PORT: '80'

Load balancing with nginx:

TCP load balancing with Nginx (SSL Pass-thru)

Enabling http2 on Debian:

How to Enable HTTP2 on Debian 8 with Nginx Web Server

Offline page setup:

Add an offline page to display when Discourse is rebuilding or starting up

This guide is intended for advanced users, who are already using nginx outside the docker container. By following this guide you make your setup more complicated and will loose some speed benefits like HTTP2 if you’re not running Ubuntu 16.04 or later. Proceed with caution! When Discourse is rebuilding or starting up, your users will usually either see an error message from their browser… [image] …or a not-so-nice 502 error message from Nginx: [image] If you’re a perfectionist l…

[Assma]

No pude encontrar respuestas claras en otros lugares.
Entendí que la instalación independiente de Discourse se recomienda por su simplicidad y robustez en entornos estándar. Sin embargo, para proporcionar alta disponibilidad, algunos sugieren expandir el modo independiente a múltiples contenedores (29413), otros rediseñan implementaciones completamente separadas.

1. Pregunta1: Dado que la alta disponibilidad se trata de duplicar servicios (web y base de datos) con conmutación por error confiable, ¿propone Discourse una solución donde tanto los servicios web como las bases de datos se repliquen dentro de los contenedores?
2. Pregunta2: Para los servicios web, se necesitaría un balanceador de carga para garantizar la equidad de carga entre las instancias. ¿Cuáles son las recomendaciones de los expertos y la comunidad de Discourse?
3. Pregunta3: Para la alta disponibilidad de bases de datos en contenedores, ¿cuál es la forma más preferible de gestionar la replicación de PostgreSQL?
4. Pregunta4: Misma pregunta para Redis.

[pfaffman (Jay Pfaffman)]

@Assma

¿Discourse propone una solución de este tipo en la que tanto los servicios web como las bases de datos se replican dentro de los contenedores?

Hay muchas maneras de lidiar con la conmutación por error de postgres. Puedes usar lo que quieras.

@Assma

¿Cuáles son las recomendaciones de los expertos y la comunidad de Discourse?

El alojamiento de CDCK utiliza HA-proxy, hasta donde yo sé. Puedes usar cualquier balanceador de carga que quieras y (en su mayoría) usar /srv/status como indicador de preparación.