I Have a gitlab requirement Standalone with HA availablity configured on 3 Vms. How should i configure them and how to connect all these HA components to the gitlab.
GitLab Reference Architectures have been designed and tested by the GitLab Quality and Support teams to provide recommended deployments at scale.
Documentation, options, and considerations on HA can be found here
In terms of HA, the smallest recommended reference architecture is for 3,000 users. There are several modifications that you can make to this architecture to reduce complexity and cost while maintaining HA. You can find more information on this topic here: Reference architecture: up to 3,000 users | GitLab
i have followed the steps but when am trying to connect gitlab with redis it says as
Failed listening on port 6379 (TCP), aborting.
oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Redis version=6.2.11, bits=64, commit=720ea82e, modified=1, pid=1674431, just started
Configuration loaded
monotonic clock: POSIX clock_gettime
Warning: Could not create server TCP listening socket ...:6379: bind: Cannot assign requested address
This is the error i get even though i have enabled the port and everything.
Your error message:
Warning: Could not create server TCP listening socket .:6379: bind: Cannot assign requested address
suggests that Redis is having trouble binding to the TCP port 6379. This could be due to a few reasons:
-
The redis instance is not reachable via TCP Configuring Redis | GitLab
-
Your system is preventing Redis from binding to the port. Make sure your firewall rules, network settings, and security groups allow connections on port 6379.
-
Another process is already using port 6379. You can check this by running
netstat -tuln | grep 6379orsudo lsof -i :6379. -
Misconfiguration or missing configuration. If things aren’t configured exactly right, this can happen. See the following resources for additional information based on your setup:
-
Redis replication and failover providing your own instance | GitLab