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/12/10 14:27:56 UTC

[GitHub] [shardingsphere] sandynz commented on pull request #14045: Separate sharding related code from scaling-core module part 3 and refactor job configuration structure

sandynz commented on pull request #14045:
URL: https://github.com/apache/shardingsphere/pull/14045#issuecomment-991018311


   There's one CI run failed, still embed ZK related:
   ```
   [INFO ] 2021-12-10 13:43:48.944 [main] o.a.s.s.c.fixture.EmbedTestingServer - Embed zookeeper server already exists 1, on 127.0.0.1:3181
   [INFO ] 2021-12-10 13:43:49.132 [main] org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:3181 sessionTimeout=60000 watcher=org.apache.curator.ConnectionState@42504d1
   [WARN ] 2021-12-10 13:43:51.315 [SyncThread:0] o.a.z.server.persistence.FileTxnLog - fsync-ing the write ahead log in SyncThread:0 took 2176ms which will adversely effect operation latency.File size is 67108880 bytes. See the ZooKeeper troubleshooting guide
   [INFO ] 2021-12-10 13:43:51.631 [main] org.apache.zookeeper.ZooKeeper - Session: 0x100001307ce0001 closed
   Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.716 s <<< FAILURE! - in org.apache.shardingsphere.scaling.core.job.ScalingJobTest
   Error:  assertExecute(org.apache.shardingsphere.scaling.core.job.ScalingJobTest)  Time elapsed: 2.532 s  <<< ERROR!
   org.apache.shardingsphere.mode.repository.cluster.ClusterPersistRepositoryException: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
   	at org.apache.shardingsphere.scaling.core.job.ScalingJobTest.assertExecute(ScalingJobTest.java:56)
   Caused by: org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
   	at org.apache.shardingsphere.scaling.core.job.ScalingJobTest.assertExecute(ScalingJobTest.java:56)
   ```
   It might be caused by `fsync-ing`, it cost 2176ms, more than operation timeout.
   
   Plan to implement Memory mode registry center implementation and use it for unit test.
   


-- 
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