Redis Persistent Storage - clear documentation of which redis databases are reuqired to persist vs can be flushed/replaced
Foreward:
I apologies if this isn't the most correct place to file this request, I'm merely looking to deploy a stable gitlab-ee active-active cluster, and the documentation as current does not make it clear if redis is a cache service, or a persistent database service. My hosting provider does not offer and persistent redis clusters, and if gitlab cannot be run without a persistent redis cluster, its going to push back / complicate our ability to become a subscribed licensee
-
Documents Feature which redis clusters must never be flushed or replaced for the lifetime of the application -
Follow-up from: #XXX, !YYY
New doc or update?
-
New documentation -
Update existing documentation
Checklists
Product Manager
-
Add the correct labels -
Add the correct milestone -
Indicate the correct document/directory for this feature -
Fill the doc blurb below
Documentation blurb
-
Doc Redis
Running with multiple Redis instances
-
Feature redis persistent storage requirement
Please declare which redis clusters must be hosted on a redis cluster that does support data persistence, or otherwise how to configure gitlab to not use redis for persistent storage
-
Feature no persistent redis hosting option in active-active deployment
Some hosted redis options may not offer data persistence, making them an incompatible choice for gitlab hosting.
(edit) documenting the failure mode of a redis flush/failure/replacement of each persistent redis cluster would also enable us to make informed decision about assuming the risk of that failure mode
Developer
-
Copy the doc blurb above and paste it into the doc -
Write the tutorial - explain how to use the feature -
Submit the MR using the appropriate MR description template