Repository navigation
About MySQL SQL Limitations Warning #20460
|
Hello, These warnings repeat 4 times in the keycloak log. It causes more than 5 minutes delay until keycloak reachable. 2023-05-19 14:28:25,288 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: node_240035, Site name: null
2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use <sql> or <modifySql> to re-specify all configuration if this is the case
2023-05-19 14:28:25,986 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use <sql> or <modifySql> to re-specify all configuration if this is the case
2023-05-19 14:28:26,433 INFO [org.keycloak.quarkus.runtime.storage.legacy.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml
2023-05-19 14:28:26,895 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, modifyDataType will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use <sql> or <modifySql> to re-specify all configuration if this is the case
2023-05-19 14:28:26,896 WARN [liquibase.changelog.DatabaseChangeLog] (main) Due to mysql SQL limitations, setNullable will lose primary key/autoincrement/not null/comment settings explicitly redefined in the change. Use <sql> or <modifySql> to re-specify all configuration if this is the case
2023-05-19 14:30:53,602 INFO [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-05-19 14:30:53,614 INFO [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realmThe database already configured for keycloak database, db user and db password. They are running in k8s, and there is no resource limit to prevent any operation. Do you have any suggestions to remove this warnings? Thanks 😊 |
Answered by
andre-nascimento6791
Jun 6, 2023
Replies: 1 comment 2 replies
|
@rection -> Thanks for the report and sorry you are facing issues with the Keycloak + MySQL in K8s. Are you using the official "Keycloak Kubernetes Operator"? Are you running in which K8s engine? I'd suggest creating a GH Issue with steps to reproduce. That'd help us a lot when triaging and investigating this issue. Thanks in advance. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well done, @rection !
Thanks for clarifying the scenario in the new Issue's description.
I'm gonna take a look at it. Follow the comments there from now.
Thanks.