Myshiner commented on issue #3030: [ERROR] Connection timed out for zookeeper 
server connection string (ip:2182) and timeout
URL: 
https://github.com/apache/incubator-shardingsphere/issues/3030#issuecomment-540421251
 
 
   @wgy8283335 the sharding-proxy and zookeeper running on a same machine with 
OS version Centos Linux release 7.5, sharding-proxy 3.1.0, zookeeper 3.4.13. 
and the error log as follow(And now i didn't get this kind error any more.)
   
   2019-09-12 18:13:14.852 [main-EventThread] ERROR 
org.apache.curator.ConnectionState - Connection timed out for connection string 
(10.10.0.193:2182) and timeout (500) / elapsed (6307)
   2019-09-12 18:13:21.411 [Curator-Framework-0] ERROR 
org.apache.curator.ConnectionState - Connection timed out for connection string 
(10.10.0.193:2182) and timeout (500) / elapsed (12865)
   2019-09-12 18:13:28.246 [Curator-Framework-0] ERROR 
org.apache.curator.ConnectionState - Connection timed out for connection string 
(10.10.0.193:2182) and timeout (500) / elapsed (19701)
   2019-09-12 18:13:34.954 [Curator-Framework-0] ERROR 
org.apache.curator.ConnectionState - Connection timed out for connection string 
(10.10.0.193:2182) and timeout (500) / elapsed (6699)
   2019-09-12 18:13:14.852 [ main-EventThread ] - [ ERROR ] [ 
org.apache.curator.ConnectionState : 200 ] - Connection timed out for 
connection string (10.10.0.193:2182) and timeout (500) / elapsed (6307)
   2019-09-12 18:13:21.411 [ Curator-Framework-0 ] - [ ERROR ] [ 
org.apache.curator.ConnectionState : 200 ] - Connection timed out for 
connection string (10.10.0.193:2182) and timeout (500) / elapsed (12865)
   2019-09-12 18:13:28.246 [ Curator-Framework-0 ] - [ ERROR ] [ 
org.apache.curator.ConnectionState : 200 ] - Connection timed out for 
connection string (10.10.0.193:2182) and timeout (500) / elapsed (19701)
   2019-09-12 18:13:34.954 [ Curator-Framework-0 ] - [ ERROR ] [ 
org.apache.curator.ConnectionState : 200 ] - Connection timed out for 
connection string (10.10.0.193:2182) and timeout (500) / elapsed (6699)
    
   Is it something to do with the poolsize of sharding-proxy, the maxPoolSize 
is set to 50. please see the datasource conf for your reference.
   neworiental_v3: 
!!io.shardingsphere.orchestration.yaml.YamlDataSourceConfiguration
     dataSourceClassName: com.zaxxer.hikari.HikariDataSource
     properties:
       url: 
jdbc:mysql://10.10.0.193:4306/neworiental_v3?serverTimezone=UTC&useSSL=false
       password: 
       maxPoolSize: 50
       maintenanceIntervalMilliseconds: 30000
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       minPoolSize: 1
       username: 
       maxLifetimeMilliseconds: 1800000
   slave_v3: !!io.shardingsphere.orchestration.yaml.YamlDataSourceConfiguration
     dataSourceClassName: com.zaxxer.hikari.HikariDataSource
     properties:
       url: 
jdbc:mysql://10.10.0.193:4306/neworiental_v3?serverTimezone=UTC&useSSL=false
       password: 
       maxPoolSize: 50
       maintenanceIntervalMilliseconds: 30000
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       minPoolSize: 1
       username: 
       maxLifetimeMilliseconds: 1800000
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to