使用 H2 内存数据库，自动初始化快速启动失败，日志并没有错误日志，请问这是什么原因？ about apollo HOT 8 OPEN

Based on the information you've provided and the context from the Apollo repository, it seems like you've followed the correct steps to initialize the H2 memory database for Apollo Quick Start versions 1.9.0, 2.1.0, and 2.2.0.

However, there was a similar issue reported in the Apollo repository titled Column "Cluster" not found error when running apollo quick start with h2. This issue was resolved by a pull request: rename the init.h2.sql to avoid loading wrong files in quick start mode. Although the specific changes made in this pull request are not detailed in the repository, it suggests that there might have been a problem with the initialization files used in quick start mode.

There could be several reasons for Apollo Quick Start failure with the H2 memory database. Some common reasons include SQL syntax compatibility issues, character set and collation settings, data type compatibility, timestamp default values, index prefix lengths, stored procedures and functions, lack of H2-specific optimizations, and configuration and version mismatches.

Unfortunately, without specific error messages or logs, it's difficult to pinpoint the exact cause of the failure you're experiencing. If possible, could you provide more detailed logs or error messages? This would help in identifying the root cause of the issue.

In the meantime, you might want to check the compatibility of your H2 database with the SQL script used by Apollo, especially if it includes platform-specific features or syntax. You could also try to ensure that your H2 database version and configuration match the expectations of the Apollo Quick Start setup.

I hope this information is helpful. Please let me know if you have any other questions or need further clarification.

Sources

• Column "Cluster" not found error when running apollo quick start with h2
• docs/en/deployment/quick-start.md
• apollo-build-sql-converter/src/test/resources/META-INF/sql/h2-test/delta/v000-v010/apolloportaldb-v000-v010-base.sql

from apollo.

你好，@wallmamami！我是Dosu，一个可以帮助你解决问题、回答问题并成为贡献者的机器人。我在这里帮助你，同时等待人类维护者的回复。现在我将开始查看你的问题，并将很快提供完整的回答。

from apollo.

这三个版本试了都是同样的问题
apollo-quick-start-1.9.0
apollo-quick-start-2.1.0
apollo-quick-start-2.2.0

from apollo.

2024-03-13 15:08:31.471 INFO 31577 --- [main] c.c.f.apollo.assembly.ApolloApplication : Starting ApolloApplication v1.9.0 using Java 1.8.0_322 on VM-12-46-tencentos with PID 31577 (/home/anymatch/apollo/quick-start/apollo-all-in-one.jar started by root in /home/anymat
ch/apollo/quick-start)
2024-03-13 15:08:31.474 INFO 31577 --- [main] c.c.f.apollo.assembly.ApolloApplication : The following profiles are active: github,auth
2024-03-13 15:08:32.606 INFO 31577 --- [main] o.s.cloud.context.scope.GenericScope : BeanFactory id=e4e7a962-7e6a-32f7-a9a2-73b8244230aa
2024-03-13 15:08:32.920 INFO 31577 --- [main] o.s.l.c.support.AbstractContextSource : Property 'userDn' not set - anonymous context will be used for read-write operations
2024-03-13 15:08:33.291 INFO 31577 --- [main] DiscoveryClientOptionalArgsConfiguration : Eureka HTTP Client uses Jersey
2024-03-13 15:08:33.378 WARN 31577 --- [main] iguration$LoadBalancerCaffeineWarnLogger : Spring Cloud LoadBalancer is currently working with the default cache. You can switch to using Caffeine cache, by adding it and org.springframework.cache.caffeine.CaffeineCacheMana
ger to the classpath.
2024-03-13 15:08:33.406 INFO 31577 --- [main] o.s.c.n.eureka.InstanceInfoFactory : Setting initial instance status as: STARTING
2024-03-13 15:08:33.431 INFO 31577 --- [main] com.netflix.discovery.DiscoveryClient : Initializing Eureka in region us-east-1
2024-03-13 15:08:33.433 INFO 31577 --- [main] com.netflix.discovery.DiscoveryClient : Client configured to neither register nor query for data.
2024-03-13 15:08:33.537 INFO 31577 --- [main] com.netflix.discovery.DiscoveryClient : Discovery Client initialized at timestamp 1710313713438 with initial instances count: 0
2024-03-13 15:08:33.542 INFO 31577 --- [main] o.s.c.n.e.s.EurekaServiceRegistry : Registering application UNKNOWN with eureka with status UP
2024-03-13 15:08:33.561 INFO 31577 --- [main] c.c.f.apollo.assembly.ApolloApplication : Started ApolloApplication in 2.713 seconds (JVM running for 3.487)
2024-03-13 15:08:33.564 INFO 31577 --- [main] c.c.f.apollo.assembly.ApolloApplication : application isActive: true
2024-03-13 15:08:33.565 INFO 31577 --- [SpringContextShutdownHook] o.s.c.n.e.s.EurekaServiceRegistry : Unregistering application UNKNOWN with eureka with status DOWN
2024-03-13 15:08:33.570 INFO 31577 --- [SpringContextShutdownHook] com.netflix.discovery.DiscoveryClient : Shutting down DiscoveryClient ...
2024-03-13 15:08:33.601 INFO 31577 --- [SpringContextShutdownHook] com.netflix.discovery.DiscoveryClient : Completed shut down of DiscoveryClient

from apollo.

It may be related to spring-cloud/spring-cloud-netflix#3570
I tests the master branch. It works well.

from apollo.

@wallmamami The apollo-all-in-one.jar was not updated to the latest version. You may try it now.

from apollo.