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 2021/10/23 01:32:56 UTC
[GitHub] [shardingsphere] linghengqian opened a new issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
linghengqian opened a new issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234
## Bug Report
**For English only**, other languages will not accept.
Before report a bug, make sure you have:
- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues).
- Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will **close it**.
Please answer these questions before submitting your issue. Thanks!
### Which version of ShardingSphere did you use?
5.0.0-RC1
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
After configuring Zookeeper's permission token, connect normally.
The following is my configuration in server.yaml.
```YAML
mode:
type: Cluster
repository:
type: ZooKeeper
props:
namespace: governance_ds
server-lists: 127.0.0.1:2181
retryIntervalMilliseconds: 500
timeToLiveSeconds: 60
maxRetries: 3
operationTimeoutMilliseconds: 500
digest: us234243er:us234354er
overwrite: true
rules:
- !AUTHORITY
users:
- shardingsphere233@%:shardingsphere213
- shard2233@:shard634876
provider:
type: ALL_PRIVILEGES_PERMITTED
- !TRANSACTION
defaultType: XA
providerType: Atomikos
props:
max-connections-size-per-query: 1
kernel-executor-size: 16
proxy-frontend-flush-threshold: 128
proxy-opentracing-enabled: false
proxy-hint-enabled: false
sql-show: false
check-table-metadata-enabled: false
lock-wait-timeout-milliseconds: 50000
show-process-list-enabled: false
proxy-backend-query-fetch-size: -1
check-duplicate-table-enabled: false
sql-comment-parse-enabled: false
proxy-frontend-executor-size: 0
proxy-backend-executor-suitable: OLAP
```
### Actual behavior
Throw an exception message and abort.
```shell
[INFO ] 2021-10-23 09:13:09.437 [main] org.apache.zookeeper.ZooKeeper - Client environment:os.memory.free=1765MB
[INFO ] 2021-10-23 09:13:09.437 [main] org.apache.zookeeper.ZooKeeper - Client environment:os.memory.max=1945MB
[INFO ] 2021-10-23 09:13:09.438 [main] org.apache.zookeeper.ZooKeeper - Client environment:os.memory.total=1945MB
[INFO ] 2021-10-23 09:13:09.444 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=113.107.163.210:7301 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@74f6c5d8
[INFO ] 2021-10-23 09:13:09.454 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-23 09:13:09.625 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-23 09:13:09.635 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-23 09:13:09.645 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-23 09:13:18.736 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 113.107.163.210/113.107.163.210:7301.
[INFO ] 2021-10-23 09:13:18.737 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[WARN ] 2021-10-23 09:13:20.803 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - Session 0x0 for sever 113.107.163.210/113.107.163.210:7301, Closing socket connection. Attempting reconnect except it is a SessionExpiredException.
java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:342)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[WARN ] 2021-10-23 09:13:30.671 [Curator-Framework-0] o.a.c.retry.ExponentialBackoffRetry - Sleep extension too large (70000). Pinning to 30000
[INFO ] 2021-10-23 09:13:30.980 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 113.107.163.210/113.107.163.210:7301.
[INFO ] 2021-10-23 09:13:30.981 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[WARN ] 2021-10-23 09:13:33.039 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - Session 0x0 for sever 113.107.163.210/113.107.163.210:7301, Closing socket connection. Attempting reconnect except it is a SessionExpiredException.
java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:342)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-23 09:13:39.656 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-23 09:13:43.234 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 113.107.163.210/113.107.163.210:7301.
[INFO ] 2021-10-23 09:13:43.235 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[WARN ] 2021-10-23 09:13:45.318 [main-SendThread(113.107.163.210:7301)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x0.
java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:342)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-23 09:13:45.430 [main] org.apache.zookeeper.ZooKeeper - Session: 0x0 closed
[INFO ] 2021-10-23 09:13:45.431 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x0
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
I have seen another closed issue.( https://github.com/apache/shardingsphere/issues/12292 )I initially thought it was a zookeeper problem, until I found out that after removing `digest: us234243er:us234354er` and removing the zookeeper configuration, the program ran normally.
Does this mean that the configuration method of the new version has changed, but the official website document does not mention it?
### Reason analyze (If you can)
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
### Example codes for reproduce this issue (such as a github link).
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] zjcnb removed a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
zjcnb removed a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950760838
Can you try change your dataDir=/tmp/zookeeper-new in your zoo.cfg.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951213292
@zjcnb According to your prompt, I am sure the same error will still be reported after switching the dataDir.
I checked the source code provided by Apache Curator and changed digest to `admin:123456`, which throws the same exception whether I change it or not.(I have reconfigured it on the cloud server. In order to facilitate the explanation of the issue, I still change the log in the log to `127.0.01:2181`)
```shell
[WARN ] 2021-10-26 02:51:56.635 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0021.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0021, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-26 02:51:56.740 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0021 closed
[INFO ] 2021-10-26 02:51:56.740 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0021
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951213292
@zjcnb According to your prompt, I am sure the same error will still be reported after switching the dataDir.
I checked the source code provided by Apache Curator and changed `digest` to `admin:123456` (like `username:password`), which throws the same exception whether I change it or not.(I have reconfigured it on the cloud server. In order to facilitate the explanation of the issue, I still change the log in the log to `127.0.01:2181`)
```shell
[WARN ] 2021-10-26 02:51:56.635 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0021.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0021, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-26 02:51:56.740 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0021 closed
[INFO ] 2021-10-26 02:51:56.740 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0021
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-954798185
With the help of @zjcnb, I confirmed the two questions corresponding to this issue. The first question is the JAR package that I used in the custom sharding algorithm class used in `CLASS_BASE`, and the `org.apache.shardingsphere:shardingsphere-jdbc-core-spring-boot-starter` is `5.0.0-beta`, which does not correspond to the `5.0.0-RC1` version of `ShardingSphere-Proxy` running this JAR, so use it instead This problem was first confirmed after `ShardingSphere-Proxy` `5.0.0-beta`.
The second problem is the situation mentioned in the article of this issue. Running `start.bat` under the `Windows` platform, can only connect to the local `zookeeper` `3.7.0`, and cannot connect to the cloud server's `zookeeper` `3.7.0`. After multiple `Windows` environment tests, it remains the same.
When starting `start.sh` in the Linux environment, it can connect to the cloud's `zookeeper` `3.7.0` normally. I ensured that the JDK used by the `windows` and `linux` environments are both `Eclipse Adoptium` `8u302`, tested three sets of `ShardingSphere-Proxy` instances and two sets of `zookeeper` instances, and verified them on three devices.
I confirmed that `digest` is normally verified by `ShardingSphere-Proxy` `5.0.0-beta`, this is no problem. After @zjcnb verification, `ShardingSphere-Proxy` `5.0.0-RC1` started normally. There is no special problem with `start.sh`, and there are still problems with the `start.bat` of testing `ShardingSphere-Proxy` `5.0.0-RC1` under my `windows 10`.
The error message under the `windows` platform is as follows.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:21:55.339 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-29 22:22:02.445 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:22:02.446 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:22:02.458 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /192.168.1.103:61474, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:22:02.481 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0047, negotiated timeout = 40000
[WARN ] 2021-10-29 22:22:02.506 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0047.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0047, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-29 22:22:02.616 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0047 closed
[INFO ] 2021-10-29 22:22:02.616 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0047
Exception in thread "main" org.apache.shardingsphere.governance.repository.api.exception.GovernanceException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:127)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:81)
at org.apache.shardingsphere.governance.core.registry.RegistryCenterRepositoryFactory.newInstance(RegistryCenterRepositoryFactory.java:49)
at org.apache.shardingsphere.governance.core.GovernanceFacade.init(GovernanceFacade.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.GovernanceBootstrapInitializer.getProxyConfiguration(GovernanceBootstrapInitializer.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.AbstractBootstrapInitializer.init(AbstractBootstrapInitializer.java:66)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:48)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:124)
... 6 more
```
The following is the normal startup log in the `linux` environment.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:03:30.173 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=127.0.0.1:2181 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@5c33f1a9
[INFO ] 2021-10-29 22:03:30.184 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-29 22:03:30.195 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-29 22:03:30.208 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-29 22:03:30.222 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:03:30.223 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:03:30.235 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-29 22:03:30.241 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /172.18.235.48:54470, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:03:30.272 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0046, negotiated timeout = 40000
[INFO ] 2021-10-29 22:03:30.286 [main-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:31.243 [main] o.apache.curator.utils.Compatibility - Using org.apache.zookeeper.server.quorum.MultipleAddresses
[INFO ] 2021-10-29 22:03:31.463 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.851 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.854 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
[INFO ] 2021-10-29 22:03:31.973 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
[INFO ] 2021-10-29 22:03:35.590 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/transactions-4.0.6.jar!/transactions-defaults.properties
[INFO ] 2021-10-29 22:03:35.592 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/shardingsphere-transaction-xa-atomikos-5.0.0-beta.jar!/transactions.properties
[WARN ] 2021-10-29 22:03:35.595 [main] c.a.icatch.provider.imp.AssemblerImp - Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_max_wait_time_on_shutdown = 9223372036854775807
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.allow_subtransactions = true
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 300000
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 50000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 300000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 172.18.235.48.tm
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 86400000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 300000
[INFO ] 2021-10-29 22:03:35.612 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery...
[INFO ] 2021-10-29 22:03:35.773 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource
[INFO ] 2021-10-29 22:03:35.796 [main] o.a.s.p.i.i.AbstractBootstrapInitializer - Database name is `MySQL`, version is `5.6.50-log`
[INFO ] 2021-10-29 22:03:36.059 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] REGISTERED
[INFO ] 2021-10-29 22:03:36.063 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] BIND: 0.0.0.0/0.0.0.0:3398
[INFO ] 2021-10-29 22:03:36.067 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f, L:/0.0.0.0:3398] ACTIVE
[INFO ] 2021-10-29 22:03:36.067 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success.
```
Another problem is that `5.0.0-beta` and `5.0.0-RC1` of `shardingsphere-proxy`, `start.bat` do not support the startup of `JDK11` and above. I am not sure whether the `master` branch has been resolved this question.
According to my test results, the `start.bat` of `shardingsphere-proxy` `5.0.0-beta` and `5.0.0-RC1` both showed abnormal conditions under the `windows` platform. Hope to have friends Can give more tests.
I will change the title of the issue in order to facilitate the search of latecomers.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian closed issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian closed issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-954798185
With the help of @zjcnb, I confirmed the two questions corresponding to this issue. The first question is the JAR package that I used in the custom sharding algorithm class used in `CLASS_BASE`, and the `org.apache.shardingsphere:shardingsphere-jdbc-core-spring-boot-starter` is `5.0.0-beta`, which does not correspond to the `5.0.0-RC1` version of `ShardingSphere-Proxy` running this JAR, so use it instead This problem was first confirmed after `ShardingSphere-Proxy` `5.0.0-beta`.
The second problem is the situation mentioned in the article of this issue. Running `start.bat` under the `Windows` platform, can only connect to the local `zookeeper` `3.7.0`, and cannot connect to the cloud server's `zookeeper` `3.7.0`. After multiple `Windows` environment tests, it remains the same.
When starting `start.sh` in the Linux environment, it can connect to the cloud's `zookeeper` `3.7.0` normally. I ensured that the JDK used by the `windows` and `linux` environments are both `Eclipse Adoptium` `8u302`, tested three sets of `ShardingSphere-Proxy` instances and two sets of `zookeeper` instances, and verified them on three devices.
I confirmed that `digest` is normally verified by `ShardingSphere-Proxy` `5.0.0-beta`, this is no problem. After @zjcnb verification, `ShardingSphere-Proxy` `5.0.0-RC1` started normally. There is no special problem with `start.sh`, and there are still problems with the `start.bat` of testing `ShardingSphere-Proxy` `5.0.0-RC1` under my `windows 10`.
The error message under the `windows` platform is as follows.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:21:55.339 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-29 22:22:02.445 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:22:02.446 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:22:02.458 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /192.168.1.103:61474, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:22:02.481 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0047, negotiated timeout = 40000
[WARN ] 2021-10-29 22:22:02.506 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0047.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0047, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-29 22:22:02.616 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0047 closed
[INFO ] 2021-10-29 22:22:02.616 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0047
Exception in thread "main" org.apache.shardingsphere.governance.repository.api.exception.GovernanceException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:127)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:81)
at org.apache.shardingsphere.governance.core.registry.RegistryCenterRepositoryFactory.newInstance(RegistryCenterRepositoryFactory.java:49)
at org.apache.shardingsphere.governance.core.GovernanceFacade.init(GovernanceFacade.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.GovernanceBootstrapInitializer.getProxyConfiguration(GovernanceBootstrapInitializer.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.AbstractBootstrapInitializer.init(AbstractBootstrapInitializer.java:66)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:48)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:124)
... 6 more
```
The following is the normal startup log in the `linux` environment.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:03:30.173 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=113.107.163.210:7500 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@5c33f1a9
[INFO ] 2021-10-29 22:03:30.184 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-29 22:03:30.195 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-29 22:03:30.208 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-29 22:03:30.222 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:03:30.223 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:03:30.235 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-29 22:03:30.241 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /172.18.235.48:54470, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:03:30.272 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0046, negotiated timeout = 40000
[INFO ] 2021-10-29 22:03:30.286 [main-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:31.243 [main] o.apache.curator.utils.Compatibility - Using org.apache.zookeeper.server.quorum.MultipleAddresses
[INFO ] 2021-10-29 22:03:31.463 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.851 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.854 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
[INFO ] 2021-10-29 22:03:31.973 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
[INFO ] 2021-10-29 22:03:35.590 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/transactions-4.0.6.jar!/transactions-defaults.properties
[INFO ] 2021-10-29 22:03:35.592 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/shardingsphere-transaction-xa-atomikos-5.0.0-beta.jar!/transactions.properties
[WARN ] 2021-10-29 22:03:35.595 [main] c.a.icatch.provider.imp.AssemblerImp - Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_max_wait_time_on_shutdown = 9223372036854775807
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.allow_subtransactions = true
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 300000
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 50000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 300000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 172.18.235.48.tm
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 86400000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 300000
[INFO ] 2021-10-29 22:03:35.612 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery...
[INFO ] 2021-10-29 22:03:35.773 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource
[INFO ] 2021-10-29 22:03:35.796 [main] o.a.s.p.i.i.AbstractBootstrapInitializer - Database name is `MySQL`, version is `5.6.50-log`
[INFO ] 2021-10-29 22:03:36.059 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] REGISTERED
[INFO ] 2021-10-29 22:03:36.063 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] BIND: 0.0.0.0/0.0.0.0:3398
[INFO ] 2021-10-29 22:03:36.067 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f, L:/0.0.0.0:3398] ACTIVE
[INFO ] 2021-10-29 22:03:36.067 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success.
```
According to my test results, the `start.bat` of `shardingsphere-proxy` `5.0.0-beta` and `5.0.0-RC1` both showed abnormal conditions under the `windows` platform. Hope to have friends Can give more tests.
I will change the title of the issue in order to facilitate the search of latecomers.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950608742
> @linghengqian which version of zookeeper did you use?
The zooKeeper version deployed on my server is 3.7.0.
Do I understand this correctly? If digest is selected, the ID of the ACL should be `username:BASE64(SHA1(password)) `instead of `username:password`?
One problem is that I also set `ZKSessionTimeout` to 20 in `ZKUI` due to the bandwidth problem of the test server. I am not sure which attribute the function of `server.yaml` corresponds to in `ShardjngSphere-Proxy`.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950608742
> @linghengqian which version of zookeeper did you use?
The zooKeeper version deployed on my server is 3.7.0.
Do I understand this correctly? If digest is selected, the ID of the ACL should be 'username:BASE64(SHA1(password))' instead of 'username:password'?
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-954798185
With the help of @zjcnb, I confirmed the two questions corresponding to this issue. The first question is the JAR package that I used in the custom sharding algorithm class used in `CLASS_BASE`, and the `org.apache.shardingsphere:shardingsphere-jdbc-core-spring-boot-starter` is `5.0.0-beta`, which does not correspond to the `5.0.0-RC1` version of `ShardingSphere-Proxy` running this JAR, so use it instead This problem was first confirmed after `ShardingSphere-Proxy` `5.0.0-beta`.
The second problem is the situation mentioned in the article of this issue. Running `start.bat` under the `Windows` platform, can only connect to the local `zookeeper` `3.7.0`, and cannot connect to the cloud server's `zookeeper` `3.7.0`. After multiple `Windows` environment tests, it remains the same.
When starting `start.sh` in the Linux environment, it can connect to the cloud's `zookeeper` `3.7.0` normally. I ensured that the JDK used by the `windows` and `linux` environments are both `Eclipse Adoptium` `8u302`, tested three sets of `ShardingSphere-Proxy` instances and two sets of `zookeeper` instances, and verified them on three devices.
I confirmed that `digest` is normally verified by `ShardingSphere-Proxy` `5.0.0-beta`, this is no problem. After @zjcnb verification, `ShardingSphere-Proxy` `5.0.0-RC1` started normally. There is no special problem with `start.sh`, and there are still problems with the `start.bat` of testing `ShardingSphere-Proxy` `5.0.0-RC1` under my `windows 10`.
The error message under the `windows` platform is as follows.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:21:55.339 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-29 22:22:02.445 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:22:02.446 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:22:02.458 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /192.168.1.103:61474, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:22:02.481 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0047, negotiated timeout = 40000
[WARN ] 2021-10-29 22:22:02.506 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0047.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0047, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-29 22:22:02.616 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0047 closed
[INFO ] 2021-10-29 22:22:02.616 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0047
Exception in thread "main" org.apache.shardingsphere.governance.repository.api.exception.GovernanceException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:127)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:81)
at org.apache.shardingsphere.governance.core.registry.RegistryCenterRepositoryFactory.newInstance(RegistryCenterRepositoryFactory.java:49)
at org.apache.shardingsphere.governance.core.GovernanceFacade.init(GovernanceFacade.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.GovernanceBootstrapInitializer.getProxyConfiguration(GovernanceBootstrapInitializer.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.AbstractBootstrapInitializer.init(AbstractBootstrapInitializer.java:66)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:48)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:124)
... 6 more
```
The following is the normal startup log in the `linux` environment.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:03:30.173 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=127.0.0.1:2181 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@5c33f1a9
[INFO ] 2021-10-29 22:03:30.184 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-29 22:03:30.195 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-29 22:03:30.208 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-29 22:03:30.222 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:03:30.223 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:03:30.235 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-29 22:03:30.241 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /172.18.235.48:54470, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:03:30.272 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0046, negotiated timeout = 40000
[INFO ] 2021-10-29 22:03:30.286 [main-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:31.243 [main] o.apache.curator.utils.Compatibility - Using org.apache.zookeeper.server.quorum.MultipleAddresses
[INFO ] 2021-10-29 22:03:31.463 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.851 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.854 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
[INFO ] 2021-10-29 22:03:31.973 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
[INFO ] 2021-10-29 22:03:35.590 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/linghengqian/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/transactions-4.0.6.jar!/transactions-defaults.properties
[INFO ] 2021-10-29 22:03:35.592 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/linghengqian/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/shardingsphere-transaction-xa-atomikos-5.0.0-beta.jar!/transactions.properties
[WARN ] 2021-10-29 22:03:35.595 [main] c.a.icatch.provider.imp.AssemblerImp - Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_max_wait_time_on_shutdown = 9223372036854775807
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.allow_subtransactions = true
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 300000
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 50000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 300000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 172.18.235.48.tm
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 86400000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 300000
[INFO ] 2021-10-29 22:03:35.612 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery...
[INFO ] 2021-10-29 22:03:35.773 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource
[INFO ] 2021-10-29 22:03:35.796 [main] o.a.s.p.i.i.AbstractBootstrapInitializer - Database name is `MySQL`, version is `5.6.50-log`
[INFO ] 2021-10-29 22:03:36.059 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] REGISTERED
[INFO ] 2021-10-29 22:03:36.063 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] BIND: 0.0.0.0/0.0.0.0:3398
[INFO ] 2021-10-29 22:03:36.067 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f, L:/0.0.0.0:3398] ACTIVE
[INFO ] 2021-10-29 22:03:36.067 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success.
```
Another problem is that `5.0.0-beta` and `5.0.0-RC1` of `shardingsphere-proxy`, `start.bat` do not support the startup of `JDK11` and above. I am not sure whether the `master` branch has been resolved this question.
According to my test results, the `start.bat` of `shardingsphere-proxy` `5.0.0-beta` and `5.0.0-RC1` both showed abnormal conditions under the `windows` platform. Hope to have friends Can give more tests.
I will change the title of the issue in order to facilitate the search of latecomers.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951947817
> @linghengqian thanks for your detailed information, could you please try without configuring `digest`? Maybe we can determine whether the problem is caused by configuring `digest`
A fact that confuses me is that although the zookeeper in the cloud removes the `digest` verification, the `shardingsphere-proxy` still cannot connect to the cloud, and there is no such problem when connecting to the local `zookeeper`.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] zjcnb commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
zjcnb commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950760838
Can you try change your dataDir=/tmp/zookeeper-new in your zoo.cfg.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950608742
> @linghengqian which version of zookeeper did you use?
The zooKeeper version deployed on my server is 3.7.0.
Do I understand this correctly? If digest is selected, the ID of the ACL should be `username:BASE64(SHA1(password)) `instead of `username:password`?
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-968675869
After the release of `shardingsphere 5.0.0` , the situation has changed. I think maybe I should close this issue and open a new issue to determine the problem.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951213292
@zjcnb According to your prompt, I am sure the same error will still be reported after switching the dataDir.
I checked the source code provided by Apache Curator and changed digest to `admin:123456`, which throws the same exception whether I change it or not.(I have reconfigured it on the cloud server. In order to facilitate the explanation of the issue, I still change the log in the log to `127.0.01:2181`)
```shell
[WARN ] 2021-10-26 02:51:56.635 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0021.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0021, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-26 02:51:56.740 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0021 closed
[INFO ] 2021-10-26 02:51:56.740 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0021
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] zjcnb commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
zjcnb commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950284012
@linghengqian Hi, Thank your feedback, Let 's me check it.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-954798185
With the help of @zjcnb, I confirmed the two questions corresponding to this issue. The first question is the JAR package that I used in the custom sharding algorithm class used in `CLASS_BASE`, and the `org.apache.shardingsphere:shardingsphere-jdbc-core-spring-boot-starter` is `5.0.0-beta`, which does not correspond to the `5.0.0-RC1` version of `ShardingSphere-Proxy` running this JAR, so use it instead This problem was first confirmed after `ShardingSphere-Proxy` `5.0.0-beta`.
The second problem is the situation mentioned in the article of this issue. Running `start.bat` under the `Windows` platform, can only connect to the local `zookeeper` `3.7.0`, and cannot connect to the cloud server's `zookeeper` `3.7.0`. After multiple `Windows` environment tests, it remains the same.
When starting `start.sh` in the Linux environment, it can connect to the cloud's `zookeeper` `3.7.0` normally. I ensured that the JDK used by the `windows` and `linux` environments are both `Eclipse Adoptium` `8u302`, tested three sets of `ShardingSphere-Proxy` instances and two sets of `zookeeper` instances, and verified them on three devices.
I confirmed that `digest` is normally verified by `ShardingSphere-Proxy` `5.0.0-beta`, this is no problem. After @zjcnb verification, `ShardingSphere-Proxy` `5.0.0-RC1` started normally. There is no special problem with `start.sh`, and there are still problems with the `start.bat` of testing `ShardingSphere-Proxy` `5.0.0-RC1` under my `windows 10`.
The error message under the `windows` platform is as follows.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:21:55.339 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-29 22:22:02.445 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:22:02.446 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:22:02.458 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /192.168.1.103:61474, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:22:02.481 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0047, negotiated timeout = 40000
[WARN ] 2021-10-29 22:22:02.506 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0047.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0047, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-29 22:22:02.616 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0047 closed
[INFO ] 2021-10-29 22:22:02.616 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0047
Exception in thread "main" org.apache.shardingsphere.governance.repository.api.exception.GovernanceException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:127)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:81)
at org.apache.shardingsphere.governance.core.registry.RegistryCenterRepositoryFactory.newInstance(RegistryCenterRepositoryFactory.java:49)
at org.apache.shardingsphere.governance.core.GovernanceFacade.init(GovernanceFacade.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.GovernanceBootstrapInitializer.getProxyConfiguration(GovernanceBootstrapInitializer.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.AbstractBootstrapInitializer.init(AbstractBootstrapInitializer.java:66)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:48)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:124)
... 6 more
```
The following is the normal startup log in the `linux` environment.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:03:30.173 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=113.107.163.210:7500 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@5c33f1a9
[INFO ] 2021-10-29 22:03:30.184 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-29 22:03:30.195 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-29 22:03:30.208 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-29 22:03:30.222 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:03:30.223 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:03:30.235 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-29 22:03:30.241 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /172.18.235.48:54470, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:03:30.272 [main-SendThread(113.107.163.210:7500)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0046, negotiated timeout = 40000
[INFO ] 2021-10-29 22:03:30.286 [main-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:31.243 [main] o.apache.curator.utils.Compatibility - Using org.apache.zookeeper.server.quorum.MultipleAddresses
[INFO ] 2021-10-29 22:03:31.463 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.851 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.854 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
[INFO ] 2021-10-29 22:03:31.973 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
[INFO ] 2021-10-29 22:03:35.590 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/transactions-4.0.6.jar!/transactions-defaults.properties
[INFO ] 2021-10-29 22:03:35.592 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/shardingsphere-transaction-xa-atomikos-5.0.0-beta.jar!/transactions.properties
[WARN ] 2021-10-29 22:03:35.595 [main] c.a.icatch.provider.imp.AssemblerImp - Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_max_wait_time_on_shutdown = 9223372036854775807
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.allow_subtransactions = true
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 300000
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 50000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 300000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 172.18.235.48.tm
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 86400000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 300000
[INFO ] 2021-10-29 22:03:35.612 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery...
[INFO ] 2021-10-29 22:03:35.773 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource
[INFO ] 2021-10-29 22:03:35.796 [main] o.a.s.p.i.i.AbstractBootstrapInitializer - Database name is `MySQL`, version is `5.6.50-log`
[INFO ] 2021-10-29 22:03:36.059 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] REGISTERED
[INFO ] 2021-10-29 22:03:36.063 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] BIND: 0.0.0.0/0.0.0.0:3398
[INFO ] 2021-10-29 22:03:36.067 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f, L:/0.0.0.0:3398] ACTIVE
[INFO ] 2021-10-29 22:03:36.067 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success.
```
According to my test results, the `start.bat` of `shardingsphere-proxy` `5.0.0-beta` and `5.0.0-RC1` both showed abnormal conditions under the `windows` platform. Hope to have friends Can give more tests.
I will change the title of the issue in order to facilitate the search of latecomers.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950331376
> @linghengqian Hi, Thank your feedback, Let 's me check it.
Hi, I'm very sorry that I only saw your message now. I checked the `org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository` of the ShardSphere-Proxy 5.0.0-RC1 source code and found that its correct configuration should be Only the id part of the ACL should be configured. But I changed the corresponding configuration in server.yaml to `digest: us234243er:shdnegzow@%=` and still reported the same. And I can access it normally through ZKUI.
An embarrassing problem is that I don’t know how ShardingSphere-Proxy breaks the point to check whether it is running normally, friends, can you help test `org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository`, here Is the `buildCuratorClient()` called by the `init()` function executed normally?
```shell
[INFO ] 2021-10-24 21:56:27.922 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000254719c001c
[INFO ] 2021-10-24 21:56:27.922 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000254719c001c closed
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] menghaoranss commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
menghaoranss commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950601584
@linghengqian which version of zookeeper did you use?
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951213292
@zjcnb According to your prompt, I am sure the same error will still be reported after switching the dataDir.
I checked the source code provided by Apache Curator and changed `digest` to `admin:123456` (like `username:password`), which throws the same exception whether I change it or not.(I have reconfigured it on the cloud server. In order to facilitate the explanation of the issue, I still change the log in the log to `127.0.0.1:2181`)
```shell
[WARN ] 2021-10-26 02:51:56.635 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0021.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0021, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-26 02:51:56.740 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0021 closed
[INFO ] 2021-10-26 02:51:56.740 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0021
Exception in thread "main" org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:128)
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:82)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.createClusterPersistRepository(ClusterContextManagerBuilder.java:115)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.beforeBuildContextManager(ClusterContextManagerBuilder.java:92)
at org.apache.shardingsphere.mode.manager.cluster.ClusterContextManagerBuilder.build(ClusterContextManagerBuilder.java:82)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.initContext(BootstrapInitializer.java:77)
at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:68)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:47)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.mode.repository.cluster.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:125)
... 7 more
```
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] menghaoranss commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
menghaoranss commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-951538637
@linghengqian thanks for your detailed information, could you please try without configuring `digest`? Maybe we can determine whether the problem is caused by configuring `digest`
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: ShardingSphere-Proxy cannot access the zookeeper in the cloud through start.bat under the windows platform
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-954798185
With the help of @zjcnb, I confirmed the two questions corresponding to this issue. The first question is the JAR package that I used in the custom sharding algorithm class used in `CLASS_BASE`, and the `org.apache.shardingsphere:shardingsphere-jdbc-core-spring-boot-starter` is `5.0.0-beta`, which does not correspond to the `5.0.0-RC1` version of `ShardingSphere-Proxy` running this JAR, so use it instead This problem was first confirmed after `ShardingSphere-Proxy` `5.0.0-beta`.
The second problem is the situation mentioned in the article of this issue. Running `start.bat` under the `Windows` platform, can only connect to the local `zookeeper` `3.7.0`, and cannot connect to the cloud server's `zookeeper` `3.7.0`. After multiple `Windows` environment tests, it remains the same.
When starting `start.sh` in the Linux environment, it can connect to the cloud's `zookeeper` `3.7.0` normally. I ensured that the JDK used by the `windows` and `linux` environments are both `Eclipse Adoptium` `8u302`, tested three sets of `ShardingSphere-Proxy` instances and two sets of `zookeeper` instances, and verified them on three devices.
I confirmed that `digest` is normally verified by `ShardingSphere-Proxy` `5.0.0-beta`, this is no problem. After @zjcnb verification, `ShardingSphere-Proxy` `5.0.0-RC1` started normally. There is no special problem with `start.sh`, and there are still problems with the `start.bat` of testing `ShardingSphere-Proxy` `5.0.0-RC1` under my `windows 10`.
The error message under the `windows` platform is as follows.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:21:55.339 [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl - backgroundOperationsLoop exiting
[INFO ] 2021-10-29 22:22:02.445 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:22:02.446 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:22:02.458 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /192.168.1.103:61474, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:22:02.481 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0047, negotiated timeout = 40000
[WARN ] 2021-10-29 22:22:02.506 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - An exception was thrown while closing send thread for session 0x1000d6a118f0047.
org.apache.zookeeper.ClientCnxn$EndOfStreamException: Unable to read additional data from server sessionid 0x1000d6a118f0047, likely server has closed socket
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:75)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:348)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1262)
[INFO ] 2021-10-29 22:22:02.616 [main] org.apache.zookeeper.ZooKeeper - Session: 0x1000d6a118f0047 closed
[INFO ] 2021-10-29 22:22:02.616 [main-EventThread] org.apache.zookeeper.ClientCnxn - EventThread shut down for session: 0x1000d6a118f0047
Exception in thread "main" org.apache.shardingsphere.governance.repository.api.exception.GovernanceException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.handler.CuratorZookeeperExceptionHandler.handleException(CuratorZookeeperExceptionHandler.java:51)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:127)
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.init(CuratorZookeeperRepository.java:81)
at org.apache.shardingsphere.governance.core.registry.RegistryCenterRepositoryFactory.newInstance(RegistryCenterRepositoryFactory.java:49)
at org.apache.shardingsphere.governance.core.GovernanceFacade.init(GovernanceFacade.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.GovernanceBootstrapInitializer.getProxyConfiguration(GovernanceBootstrapInitializer.java:58)
at org.apache.shardingsphere.proxy.initializer.impl.AbstractBootstrapInitializer.init(AbstractBootstrapInitializer.java:66)
at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:48)
Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.shardingsphere.governance.repository.zookeeper.CuratorZookeeperRepository.initCuratorClient(CuratorZookeeperRepository.java:124)
... 6 more
```
The following is the normal startup log in the `linux` environment.(In order to facilitate the display of the issue, I still use `127.0.0.1` to replace the `ip` of `log`)
```shell
[INFO ] 2021-10-29 22:03:30.173 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=127.0.0.1:2181 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@5c33f1a9
[INFO ] 2021-10-29 22:03:30.184 [main] org.apache.zookeeper.common.X509Util - Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation
[INFO ] 2021-10-29 22:03:30.195 [main] o.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes
[INFO ] 2021-10-29 22:03:30.208 [main] org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false
[INFO ] 2021-10-29 22:03:30.222 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Opening socket connection to server 127.0.0.1/127.0.0.1:2181.
[INFO ] 2021-10-29 22:03:30.223 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error)
[INFO ] 2021-10-29 22:03:30.235 [main] o.a.c.f.imps.CuratorFrameworkImpl - Default schema
[INFO ] 2021-10-29 22:03:30.241 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Socket connection established, initiating session, client: /172.18.235.48:54470, server: 127.0.0.1/127.0.0.1:2181
[INFO ] 2021-10-29 22:03:30.272 [main-SendThread(127.0.0.1:2181)] org.apache.zookeeper.ClientCnxn - Session establishment complete on server 127.0.0.1/127.0.0.1:2181, session id = 0x1000d6a118f0046, negotiated timeout = 40000
[INFO ] 2021-10-29 22:03:30.286 [main-EventThread] o.a.c.f.state.ConnectionStateManager - State change: CONNECTED
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:30.333 [main-EventThread] o.a.c.framework.imps.EnsembleTracker - New config event received: {}
[INFO ] 2021-10-29 22:03:31.243 [main] o.apache.curator.utils.Compatibility - Using org.apache.zookeeper.server.quorum.MultipleAddresses
[INFO ] 2021-10-29 22:03:31.463 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.851 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.854 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
[INFO ] 2021-10-29 22:03:31.959 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
[INFO ] 2021-10-29 22:03:31.973 [main] com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
[INFO ] 2021-10-29 22:03:35.590 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/transactions-4.0.6.jar!/transactions-defaults.properties
[INFO ] 2021-10-29 22:03:35.592 [main] c.a.icatch.provider.imp.AssemblerImp - Loaded jar:file:/home/heqiheng/apache-shardingsphere-5.0.0-beta-shardingsphere-proxy-bin/lib/shardingsphere-transaction-xa-atomikos-5.0.0-beta.jar!/transactions.properties
[WARN ] 2021-10-29 22:03:35.595 [main] c.a.icatch.provider.imp.AssemblerImp - Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
Thanks for using Atomikos! Evaluate http://www.atomikos.com/Main/ExtremeTransactions for advanced features and professional support
or register at http://www.atomikos.com/Main/RegisterYourDownload to disable this message and receive FREE tips & advice
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_max_wait_time_on_shutdown = 9223372036854775807
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.allow_subtransactions = true
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.recovery_delay = 300000
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.automatic_resource_registration = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_max_retries = 5
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.client_demarcation = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.threaded_2pc = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.serial_jta_transactions = false
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_dir = ./logs
[INFO ] 2021-10-29 22:03:35.609 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.rmi_export_class = none
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_actives = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.checkpoint_interval = 50000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.enable_logging = true
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.log_base_name = xa_tx
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.max_timeout = 300000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.trust_client_tm = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.factory.initial = com.sun.jndi.rmi.registry.RegistryContextFactory
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.tm_unique_name = 172.18.235.48.tm
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.forget_orphaned_log_entries_delay = 86400000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.oltp_retry_interval = 10000
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: java.naming.provider.url = rmi://localhost:1099
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.force_shutdown_on_vm_exit = false
[INFO ] 2021-10-29 22:03:35.610 [main] c.a.icatch.provider.imp.AssemblerImp - USING: com.atomikos.icatch.default_jta_timeout = 300000
[INFO ] 2021-10-29 22:03:35.612 [main] c.a.icatch.provider.imp.AssemblerImp - Using default (local) logging and recovery...
[INFO ] 2021-10-29 22:03:35.773 [main] c.a.d.xa.XATransactionalResource - resource-1-ds_0: refreshed XAResource
[INFO ] 2021-10-29 22:03:35.796 [main] o.a.s.p.i.i.AbstractBootstrapInitializer - Database name is `MySQL`, version is `5.6.50-log`
[INFO ] 2021-10-29 22:03:36.059 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] REGISTERED
[INFO ] 2021-10-29 22:03:36.063 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f] BIND: 0.0.0.0/0.0.0.0:3398
[INFO ] 2021-10-29 22:03:36.067 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xca09a11f, L:/0.0.0.0:3398] ACTIVE
[INFO ] 2021-10-29 22:03:36.067 [main] o.a.s.p.frontend.ShardingSphereProxy - ShardingSphere-Proxy start success.
```
According to my test results, the `start.bat` of `shardingsphere-proxy` `5.0.0-beta` and `5.0.0-RC1` both showed abnormal conditions under the `windows` platform. Hope to have friends Can give more tests.
I will change the title of the issue in order to facilitate the search of latecomers.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian commented on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian commented on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950608742
> @linghengqian which version of zookeeper did you use?
The zooKeeper version deployed on my server is 3.7.0.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] linghengqian edited a comment on issue #13234: After configuring the digest of ShardingSphere-Proxy, I cannot connect to Zookeeper.
Posted by GitBox <gi...@apache.org>.
linghengqian edited a comment on issue #13234:
URL: https://github.com/apache/shardingsphere/issues/13234#issuecomment-950608742
> @linghengqian which version of zookeeper did you use?
The zookeeper version deployed on my server is 3.7.0.
Do I understand this correctly? If digest is selected, the ID of the ACL should be `username:BASE64(SHA1(password)) `instead of `username:password`?
One problem is that I also set `zkSessionTimeout` to 20 in `ZKUI` due to the bandwidth problem of the test server. I am not sure which attribute the function of `server.yaml` corresponds to in `ShardjngSphere-Proxy`.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org