search

mgtv-tech / redis-GunYu

Apache License 2.0
214 stars 31 forks source link

question: etcd is configured in the yaml file. When etcd was not started, GunYu got stuck when starting without reporting any errors. #69

Open erwadba opened 1 week ago

erwadba commented 1 week ago

GunYu log. 

[root@192-168-10-181 redisGunYu]# ./redisGunYu -conf ./config.yaml -cmd=sync
2024-10-22 08:48:13     info    cmd/syncer.go:85        [SyncerCommand] syncer command
2024-10-22 08:48:13     info    cmd/syncer_api.go:95    [SyncerCommand] start grpc and http server, listening on 0.0.0.0:18001
2024-10-22 08:48:13     info    cmd/syncer.go:860       [SyncerCommand] cronjob, check typology of redis cluster : input([192.168.10.179:7001 192.168.10.180:7001 192.168.10.181:7001 192.168.10.182:7001 192.168.10.183:7001 192.168.10.184:7001 192.168.10.185:7001 192.168.10.186:7001]), output([192.168.10.189:7001 192.168.10.19:7001 192.168.10.190:7001 192.168.10.191:7001 192.168.10.192:7001 192.168.10.193:7001 192.168.10.194:7001 192.168.10.195:7001]), watch(true, true), ticker(30s), txnMode(true)

If etcd does not start, can report an error in gunyu log?

ikenchina commented 1 week ago

Yep, thanks. It is due to etcd client, DialTimeout configuration doesn't work. We would be glad if you could fix it. BTW, etcd configuration is optional if you want to setup a cluster gunyu. If the config is empty, source redis will be used to implement locking and registry.