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

[2.2.x] Graceful Shutdown Refactoring #1154 #1347

Merged

Conversation

ryanemerson
Copy link
Contributor

No longer explicitly delete pods on GracefulShutdown, instead scale the StatefulSet once all of the caches have been shutdown on the server.

@ryanemerson ryanemerson force-pushed the gracefulshutdown_refactor_2.2.x branch from ffb0010 to 748d184 Compare December 9, 2021 12:37
Copy link
Collaborator

@rigazilla rigazilla left a comment

Choose a reason for hiding this comment

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

lgtm

shutdown(internalCaches);
cachesToShutdown.addAll(icr.getInternalCacheNames());
cachesToShutdown.addAll(cacheManager.getCacheNames());
shutdown(cachesToShutdown);
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't we define the shutdown function before invoking it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Where the function is defined doesn't matter in Javascript. Executing this doesn't throw an error for me.

@ryanemerson ryanemerson force-pushed the gracefulshutdown_refactor_2.2.x branch 2 times, most recently from 113aab9 to d95edcf Compare December 9, 2021 18:33
@Crumby
Copy link
Collaborator

Crumby commented Dec 10, 2021

@ryanemerson Would it make sense to update gracefulShutdown test to use 2 nodes? The test itself would uncover the issue if executed on OpenShift 4.9+

@ryanemerson ryanemerson force-pushed the gracefulshutdown_refactor_2.2.x branch 4 times, most recently from 30ddfcf to 304c89d Compare December 10, 2021 11:58
@ryanemerson
Copy link
Contributor Author

Would it make sense to update gracefulShutdown test to use 2 nodes? The test itself would uncover the issue if executed on OpenShift 4.9+

I've increased the number of nodes to 2, but the test won't fail unless we add a write to one of the caches that encounters the exception. Obviously I can't add that test to the CI until we have a new server image with the fix, so I think I'll create a follow up PR with this change

@ryanemerson ryanemerson force-pushed the gracefulshutdown_refactor_2.2.x branch 2 times, most recently from 1a73b3b to 7458a85 Compare December 13, 2021 11:04
@@ -37,7 +37,7 @@ spec:
fieldRef:
fieldPath: metadata.namespace
- name: RELATED_IMAGE_OPENJDK
value: "quay.io/infinispan/server:13.0.1.Final"
value: "quay.io/infinispan/server:13.0.2.Final"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shouldn't this be 13.0.3?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 It wasn't available when I created the PR and was required for CI. I'll be changing this to 13.0.3.Final as part of the release commit.

@ryanemerson ryanemerson changed the title Graceful Shutdown Refactoring #1154 [2.2.x] Graceful Shutdown Refactoring #1154 Dec 20, 2021
@ryanemerson ryanemerson force-pushed the gracefulshutdown_refactor_2.2.x branch from 7458a85 to bac098b Compare December 20, 2021 19:31
@ryanemerson ryanemerson merged commit 031c9af into infinispan:2.2.x Dec 22, 2021
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.

None yet

4 participants