Closed likeitchen closed 1 year ago
Hi @likeitchen , thanks for your feddback.
Did you try latest version 5.2.1
?
BTW, host: "0.0.0.0"
looks strange in Prometheus
section, it's used in server configuration usually.
Closed due to no response. If this problem persists, please reopen it or submit a new one.
Environmental information
Description of the problem
plugins: Prometheus: host: "0.0.0.0" port: 9090 props: JVM_INFORMATION_COLLECTOR_ENABLED : "true" Jaeger: host: "localhost" port: 5775 props: SERVICE_NAME: "shardingsphere" JAEGER_SAMPLER_TYPE: "const" JAEGER_SAMPLER_PARAM: "1" Zipkin: host: "localhost" port: 9411 props: SERVICE_NAME: "shardingsphere" URL_VERSION: "/api/v2/spans" SAMPLER_TYPE: "const" SAMPLER_PARAM: "1" OpenTracing: props: OPENTRACING_TRACER_CLASS_NAME: "org.apache.skywalking.apm.toolkit.opentracing.SkywalkingTracer" OpenTelemetry: props: otel.resource.attributes: "service.name=shardingsphere" otel.traces.exporter: "zipkin" Logging: props: LEVEL: "INFO"
[INFO ] 2022-11-30 09:28:07.269 [main] org.quartz.impl.StdSchedulerFactory - Quartz scheduler '_finished_check' initialized from an externally provided properties instance. [INFO ] 2022-11-30 09:28:07.269 [main] org.quartz.impl.StdSchedulerFactory - Quartz scheduler version: 2.3.2 [INFO ] 2022-11-30 09:28:07.426 [main] org.quartz.core.QuartzScheduler - Scheduler _finishedcheck$_NON_CLUSTERED started. [INFO ] 2022-11-30 09:28:07.428 [main] o.a.s.d.p.a.e.AbstractLifecycleExecutor - start lifecycle executor: org.apache.shardingsphere.data.pipeline.core.execute.PipelineJobExecutor@79631db0 [INFO ] 2022-11-30 09:28:07.432 [main] o.a.s.d.p.s.r.RuleAlteredJobWorker - worker initialization done [INFO ] 2022-11-30 09:28:07.495 [main] o.a.s.p.v.ShardingSphereProxyVersion - Database name is
MySQL
, version is8.0.29
, database name isclouddemo
[INFO ] 2022-11-30 09:28:08.128 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy Cluster mode started successfully [INFO ] 2022-11-30 09:29:30.071 [_finished_check_Worker-1] o.a.c.f.imps.CuratorFrameworkImpl - Starting [INFO ] 2022-11-30 09:29:30.072 [_finished_check_Worker-1] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=awecloud-dbproxy-zookeeper.devops:2181 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@4ae170e2 [INFO ] 2022-11-30 09:29:30.072 [_finished_check_Worker-1] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes [INFO ] 2022-11-30 09:29:30.073 [_finished_check_Worker-1] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false [INFO ] 2022-11-30 09:29:30.074 [_finished_check_Worker-1] o.a.c.f.imps.CuratorFrameworkImpl - Default schema [INFO ] 2022-11-30 09:29:30.084 [_finished_check_Worker-1-SendThread(awecloud-dbproxy-zookeeper.devops:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server awecloud-dbproxy-zookeeper.devops/10.3.149.211:2181. [INFO ] 2022-11-30 09:29:30.084 [_finished_check_Worker-1-SendThread(awecloud-dbproxy-zookeeper.devops:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error) [INFO ] 2022-11-30 09:29:30.085 [_finished_check_Worker-1-SendThread(awecloud-dbproxy-zookeeper.devops:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /10.2.1.254:49978, server: awecloud-dbproxy-zookeeper.devops/10.3.149.211:2181 [INFO ] 2022-11-30 09:29:30.088 [_finished_check_Worker-1-SendThread(awecloud-dbproxy-zookeeper.devops:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server awecloud-dbproxy-zookeeper.devops/10.3.149.211:2181, session id = 0x1000001d0000011, negotiated timeout = 40000 [INFO ] 2022-11-30 09:29:30.088 [_finished_check_Worker-1-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED [INFO ] 2022-11-30 09:29:30.090 [_finished_check_Worker-1-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {} [INFO ] 2022-11-30 09:29:30.090 [_finished_check_Worker-1-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {} Wed Nov 30 09:33:06 UTC 2022 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.