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

use rolling restart of pods for rosa scaling benchmark #817

Merged
merged 1 commit into from
May 16, 2024

Conversation

kami619
Copy link
Contributor

@kami619 kami619 commented May 15, 2024

  • using rolling restart to reset memory of the pods after the dataset creation
  • plugged it into the github workflow

I ran it on my github fork here are the results : https://github.com/kami619/keycloak-benchmark/actions/runs/9098888946/job/25010163982

fixes #799

@kami619 kami619 requested a review from ahus1 May 15, 2024 15:50
@kami619
Copy link
Contributor Author

kami619 commented May 15, 2024

Here is a sample output of the script, thats run from my local.

INFO:2024-05-15-11:36:52-EDT Deleting all Keycloak pods in sequence
NAME         READY   STATUS    RESTARTS   AGE
keycloak-0   1/1     Running   0          6m24s
keycloak-1   1/1     Running   0          6m3s
keycloak-2   1/1     Running   0          5m41s
INFO:2024-05-15-11:36:54-EDT Killing Pod 'keycloak-0'
pod "keycloak-0" deleted
deployment.apps/keycloak-operator condition met
keycloak.k8s.keycloak.org/keycloak condition met
INFO:2024-05-15-11:37:14-EDT Keycloak pod keycloak-0 took 18 seconds to recover
NAME         READY   STATUS    RESTARTS   AGE
keycloak-0   1/1     Running   0          19s
keycloak-1   1/1     Running   0          6m24s
keycloak-2   1/1     Running   0          6m2s
INFO:2024-05-15-11:37:15-EDT Killing Pod 'keycloak-1'
pod "keycloak-1" deleted
deployment.apps/keycloak-operator condition met
keycloak.k8s.keycloak.org/keycloak condition met
INFO:2024-05-15-11:37:35-EDT Keycloak pod keycloak-1 took 19 seconds to recover
NAME         READY   STATUS    RESTARTS   AGE
keycloak-0   1/1     Running   0          39s
keycloak-1   1/1     Running   0          19s
keycloak-2   1/1     Running   0          6m22s
INFO:2024-05-15-11:37:35-EDT Killing Pod 'keycloak-2'
pod "keycloak-2" deleted
deployment.apps/keycloak-operator condition met
jfbkeycloak.k8s.keycloak.org/keycloak condition met
INFO:2024-05-15-11:37:56-EDT Keycloak pod keycloak-2 took 19 seconds to recover
NAME         READY   STATUS    RESTARTS   AGE
keycloak-0   1/1     Running   0          60s
keycloak-1   1/1     Running   0          40s
keycloak-2   1/1     Running   0          19s
INFO:2024-05-15-11:37:56-EDT All Keycloak pods have been processed.

Copy link
Contributor

@ahus1 ahus1 left a comment

Choose a reason for hiding this comment

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

Thank you for the updated scripts and the link to the test run!

@ahus1 ahus1 merged commit 77b7849 into keycloak:main May 16, 2024
2 checks passed
@kami619 kami619 deleted the is-799-safe-restart-pods branch May 16, 2024 13:17
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

Successfully merging this pull request may close these issues.

After a restart of Keycloak, the Route 53 health check might have failed
2 participants