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

Warning about global state on start #27718

Closed
shawkins opened this issue Mar 8, 2024 · 7 comments
Closed

Warning about global state on start #27718

shawkins opened this issue Mar 8, 2024 · 7 comments

Comments

@shawkins
Copy link
Contributor

shawkins commented Mar 8, 2024

On a simple start or start-dev the logs will show:

2024-02-27 11:47:21,993 WARN [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled

Neither of our built-in cache configs have global-state defined, but the ClusterPermissionMapper and the ClusterRoleMapper create internal caches that expect persistence. For dev mode there doesn't seem to be a great way to ignore this, and it doesn't like we should be configuing a global-store in that case. @mhajas @mabartos @vmuzikar is there any benefit to users configuring a global-state when not in dev mode? If not, then it seems like we'd want the upstream to switch this to a debug message instead.

Originally posted by @shawkins in #27308 (comment)

@shawkins
Copy link
Contributor Author

@tristantarrant can you weigh in on if there is any benefit for keycloak to configure a global state, or if we should look to omit this warning in some way?

@tristantarrant
Copy link

Are you enabling authorization ?

@shawkins
Copy link
Contributor Author

@tristantarrant No. We by default provide configuration for infinispan in local and clustered mode https://github.com/keycloak/keycloak/tree/main/quarkus/runtime/src/main/resources - neither have explicit configuration for authorization.

@shawkins
Copy link
Contributor Author

@tristantarrant can you confirm that if we aren't using authorization, then this warning isn't meaningful? If that's the case, should there be an upstream change to detect this and lessen the warning, or should we look to do log filtering on the keycloak side?

@tristantarrant
Copy link

@shawkins
Copy link
Contributor Author

Thank you @tristantarrant

We'll close this issue when we pick up that fix.

@vmuzikar vmuzikar added priority/normal kind/bug Categorizes a PR related to a bug labels Mar 21, 2024
@shawkins
Copy link
Contributor Author

shawkins commented May 8, 2024

Resolved by #29069

@shawkins shawkins closed this as completed May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants