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

#2382 - Redis recovery command #2469

Merged
merged 8 commits into from
Nov 2, 2023
Merged

#2382 - Redis recovery command #2469

merged 8 commits into from
Nov 2, 2023

Conversation

guru-aot
Copy link
Contributor

@guru-aot guru-aot commented Nov 1, 2023

Created a make command from the below recommendation from the Redis channel in rocket chat and it seems to recover our Redis without deleting it completely in the environment and creating them again.

image

Note: This command had to be run every time, when we put down the Redis manually or any disruptions that restart the Redis pods. Parallel to this, if we have a Sysdig alert which checks the health of the Redis pods in the environment, would help us in any delays to the application queues processing.

Also wiki has been appropriately updated
https://github.com/bcgov/SIMS/wiki/DevOps-and-Running-the-Application#redis-cluster-failing-to-recover

Copy link

@cditcher cditcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be a colon

Copy link
Collaborator

@dheepak-aot dheepak-aot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Great work 👍

Copy link
Contributor

@ann-aot ann-aot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Collaborator

@andrewsignori-aot andrewsignori-aot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work and research. Just a few clarifications and please lets have a demo to see Redis being recovered using this approach.

@guru-aot guru-aot changed the title #2382-Redis recovery command #2382 - Redis recovery command Nov 1, 2023
Copy link
Contributor

@andrepestana-aot andrepestana-aot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

steps:
- name: Print env
run: |
echo NAMESPACE: $NAMESPACE
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub will not print a value that came from a secret so there is no point in printing it, IMO.

ref: ${{ inputs.gitRef }}
- name: Log in to OpenShift
run: |
oc login --token=${{ secrets.SA_TOKEN }} --server=https://api.silver.devops.gov.bc.ca:6443
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use the below instead.

oc login --token=${{ secrets.SA_TOKEN }} --server=${{ vars.OPENSHIFT_CLUSTER_URL }}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Every GitHub action is "categorized" as "env-setup" or "release" which adds a prefix to the file name and to the name itself.
Can we rename this file to env-setup-redis-recovery.yml and the name to Env Setup - Redis recovery in Openshift

Copy link

sonarqubecloud bot commented Nov 2, 2023

Please retry analysis of this Pull-Request directly on SonarCloud.

Copy link

github-actions bot commented Nov 2, 2023

E2E Workflow Workers Coverage Report

Totals Coverage
Statements: 52.62% ( 341 / 648 )
Methods: 50% ( 40 / 80 )
Lines: 56.85% ( 282 / 496 )
Branches: 26.39% ( 19 / 72 )

Copy link

github-actions bot commented Nov 2, 2023

E2E Queue Consumers Coverage Report

Totals Coverage
Statements: 76.94% ( 564 / 733 )
Methods: 71.59% ( 63 / 88 )
Lines: 78.75% ( 493 / 626 )
Branches: 42.11% ( 8 / 19 )

Copy link

github-actions bot commented Nov 2, 2023

Backend Unit Tests Coverage Report

Totals Coverage
Statements: 18.18% ( 2341 / 12879 )
Methods: 9.28% ( 151 / 1628 )
Lines: 20.7% ( 2016 / 9741 )
Branches: 11.52% ( 174 / 1510 )

Copy link

github-actions bot commented Nov 2, 2023

E2E SIMS API Coverage Report

Totals Coverage
Statements: 55.53% ( 4084 / 7354 )
Methods: 52.88% ( 505 / 955 )
Lines: 60.25% ( 3310 / 5494 )
Branches: 29.72% ( 269 / 905 )

Copy link
Collaborator

@andrewsignori-aot andrewsignori-aot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks again for adding the GitHub action, looks good 👍

@guru-aot guru-aot merged commit 0f09bb2 into main Nov 2, 2023
@guru-aot guru-aot deleted the #2382_Redis_recovery_command branch November 2, 2023 18:47
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 18:56 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 18:58 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 18:58 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 18:58 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 18:58 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 19:00 — with GitHub Actions Inactive
@guru-aot guru-aot temporarily deployed to DEV November 2, 2023 19:00 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Devops Devops
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants