You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/03/08 13:29:15 UTC

[GitHub] [incubator-shardingsphere] xunux commented on issue #4661: [bug] sharding-jdbc 4.0 version, dml sql hung up when i close master node when i use master slave write-read split function on postgresql 12

xunux commented on issue #4661: [bug] sharding-jdbc 4.0 version, dml sql hung up when i close master node when i use master slave write-read split function on postgresql 12
URL: https://github.com/apache/incubator-shardingsphere/issues/4661#issuecomment-596205913
 
 
   怕你们看不懂我写的英文,中文再描述下:
   
   我用的是 shardingsphere 4.0 版本,想用来 postgres 读写分离,发现在主节点关掉后,插入更新删除数据会堵住无响应,java 后台一直在报jdbc连接拒绝,druid连接池打印出来的错误信息“errotCode 0, state 08001”,druid 连接池设置的 maxWait 时间是60秒,直到差不多 90 秒后才报错。
   
   神奇的是,此时我若是重新启动pg主节点,启动前90秒内发起的写操作请求竟然会操作成功。
   
   sharding sphere 的 master slave 数据源若配置成同一个 pg 实例但不同库时,pg节点关闭会立马报错,与不用 shardingsphere的效果一样。
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services