Hi all, We would like to deploy Gitlab 7.1.1 in production with a loadbalancing at all levels of the infrastructure to ensure a good availability of the service.
We have have been able to setup two front servers with a loadbalancing, but we noticed that Gitlab 7.1.1 is relying on Redis 2.8.2 which cannot be loadbalanced, as far as we have understood. This is for us a kind of blocking point for the deployment in production. We are currently thinking about a way to solve this issue. We see the following possible solutions: - *solution 1*: use the standard installation (Gitlab 7.1.1 + Redis 2.8.2): does someone have experience with Redis 2.8.2 in production with a loadbalancing between the Redis servers ? If it is not possible to have a loadbalancing, which architecture did you define ? One primary server as active Redis server, and another one as passive server ? Which data do you save / replicate on the Redis servers ? - *solution 2*: wait for a Gitlab version compliant with Redis 3.0 (not yet available). May I ask you if it is already planned in the Gitlab roadmap to include Redis 3.0 ? If yes, for which version ? *- solution 3*: Gitlab 7.1.1 and Redis 3.0 Did someone test Gitlab 7.1.1 with the release candidates of Redis 3.0 ? It is compliant ? Could we plan to go in production with Gitlab 7.1.1 and Redis 3.0 ? Thanks -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/ff72bbbc-cdc0-4432-8e12-e1903a78e832%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
