linghengqian commented on issue #34068: URL: https://github.com/apache/shardingsphere/issues/34068#issuecomment-2544576585
- I will say that I cannot reproduce your problem at https://github.com/linghengqian/demo/commit/ef6342b0e93346ed0335ec38a92b2cb330f5b0e4. ```shell sdk install java 23-open sdk use java 23-open git clone [email protected]:apache/shardingsphere.git cd ./shardingsphere/ git reset --hard 2108a520547aa5fe14babe9c4eaea7e920507427 ./mvnw clean install -Prelease -T1C -DskipTests -Djacoco.skip=true -Dcheckstyle.skip=true -Drat.skip=true -Dmaven.javadoc.skip=true cd ../ git clone [email protected]:linghengqian/demo.git cd ./demo/ ./mvnw clean spring-boot:run ``` - I executed `Ctrl+C` 1 minute after startup to ensure that the shardingsphere metadata was fully loaded. If you don't execute SQL additionally, it is obviously unknown when shardingsphere will finish loading the metadata, because the h2database in memory mode is not as performant as you think. ```shell 2024-12-16 12:25:31.937 INFO 75588 --- [ main] com.java.encrypt.demo.DemoApplication : Started DemoApplication in 2.948 seconds (JVM running for 3.217) ^C2024-12-16 12:26:23.561 INFO 75588 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated... 2024-12-16 12:26:23.564 INFO 75588 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed. ``` - There is clearly a problem with your dependency management. Shardingsphere uses snakeyaml 2.2, which is stated at https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/spring-boot/#special-handling-for-earlier-versions-of-spring-boot-oss-2 . - The h2database version you are using is a bit scary. By default, the stand-alone mode of shardingsphere uses h2database instead of zookeeper to save metadata. Using an old version of h2database with memory leak problems is obviously too dangerous. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
