Alta Disponibilidade do 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]

Não consegui encontrar respostas próximas em outros lugares.
Entendi que a instalação autônoma do Discourse é recomendada por sua simplicidade e robustez em ambientes padrão. No entanto, para fornecer Alta Disponibilidade (HA), alguns sugerem expandir o modo autônomo para vários contêineres (29413), outros redesenham implantações totalmente separadas.

1. Pergunta 1: Como HA é sobre duplicar serviços (web e banco de dados) com failover confiável, o Discourse propõe tal solução onde tanto os serviços web quanto os bancos de dados são replicados dentro de contêineres?
2. Pergunta 2: Para os serviços web, um balanceador de carga seria necessário para garantir a equidade de carga entre as instâncias. Quais são as recomendações dos especialistas e da comunidade Discourse?
3. Pergunta 3: Para HA de banco de dados em contêineres, qual é a maneira mais preferível de gerenciar a replicação do PostgreSQL?
4. Pergunta 4: Mesma pergunta para o Redis.

[pfaffman (Jay Pfaffman)]

@Assma

O Discourse propõe tal solução onde tanto web-services quanto bancos de dados são replicados dentro de contêineres?

Existem várias maneiras de lidar com o failover do postgres. Você pode usar o que quiser.

@Assma

Quais são as recomendações dos especialistas e da comunidade do Discourse?

A hospedagem CDCK usa HA-proxy, pelo que me lembro. Você pode usar qualquer balanceador de carga que quiser e (na maioria das vezes) usar /srv/status como um indicador de prontidão.