Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Redis version and increase Memory #4253

Open
5 tasks
ninosamson opened this issue Jan 16, 2025 · 2 comments
Open
5 tasks

Upgrade Redis version and increase Memory #4253

ninosamson opened this issue Jan 16, 2025 · 2 comments
Assignees

Comments

@ninosamson
Copy link
Collaborator

ninosamson commented Jan 16, 2025

The current Redis Cluster has been causing issues eventually and requires manual intervention. An effort should be executed to ensure the cluster is correctly configured, can support eventual faulted nodes, and recover without intervention. Also, the amount of resources allocated to execute the cluster can potentially be pretty low and must be adjusted.

  • Upgrade Redis version. Review whether an upgrade to the latest version can be applied. Otherwise, we can upgrade to the most recent and backward-compatible version and plan a major upgrade later.
  • Check the current resource configuration for Redis Cluster execution. This document can be a starting point.
  • Review the current cluster structure (3 masters, 3 slaves) to revalidate if it is still the best approach. It seems that losing one node is making the entire cluster unstable and requiring manual intervention.
  • Try to find references in other BC Gov projects and the BC Gov community.
  • If Change Redis Persistence to RDB #2459 isn't completed it can be done as part of this effort, time allowing.
@ninosamson ninosamson added the Business Items under Business Consideration label Jan 16, 2025
@CarlyCotton
Copy link
Collaborator

Likely a timeboxed activity as analysis is required. Should do sooner than later but may not have time for 2.4 release.

@CarlyCotton CarlyCotton added this to the Full-Time "Asset" milestone Jan 16, 2025
@CarlyCotton CarlyCotton added Dev & Architecture Development and Architecture and removed Business Items under Business Consideration labels Jan 16, 2025
@andrewsignori-aot andrewsignori-aot removed the Dev & Architecture Development and Architecture label Jan 16, 2025
@ninosamson
Copy link
Collaborator Author

Tagging to 2.5 as we pulled this into sprint late to get a head start.

github-merge-queue bot pushed a commit that referenced this issue Jan 29, 2025
Team, the below files are copied from bitnami
(https://github.com/bitnami/charts/tree/main/bitnami/redis-cluster) for
the charts, so please ignore the review on these files below

![image](https://github.com/user-attachments/assets/20eba934-660b-45ab-bcd4-feb629cb72cf)
or in folders 
> base files in devops/helm/redis-cluster
> devops/helm/redis-cluster/templates

Make file is created for easy installtion of helm charts.

The values.yaml overridden with values from the values-{NAMESPACE}.yaml.
The recommendation values are not given in the
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
link given, but as per the examples, redis cluster starts at a minimum
configuration of Nano where the values are given in this
https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15.

I will create a the next PR with the actual values for namespaces
values-{NAMESPACE}.yaml.

To enable the github action initial commit of the file is created.

NOTE: Additional file changes
sources/camunda-docker-compose-core.yml - missed network type
sources/packages/forms/Dockerfile.dev is changed to enable development
environment login
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants