I am running ./cadence-server
start and I get the following error:
{"level":"fatal","ts":"2020-07-10T11:25:48.081-0400","msg":"unable to bootstrap ringpop","error":"join duration of 45.640809278s exceeded max 30s"
I am running ./cadence-server
start and I get the following error:
{"level":"fatal","ts":"2020-07-10T11:25:48.081-0400","msg":"unable to bootstrap ringpop","error":"join duration of 45.640809278s exceeded max 30s"
Make sure bootstrapHosts is configured correctly in ringpop section of the config:
ringpop:
name: cadence
bootstrapMode: hosts
bootstrapHosts: ["127.0.0.1:7933"]
maxJoinDuration: 30s
I see
ringpop:
name: cadence
bootstrapMode: hosts
bootstrapHosts: ["127.0.0.1:7933", "127.0.0.1:7934", "127.0.0.1:7935"]
maxJoinDuration: 30s
Should I change this setting if I am running cadence-server start
?
How are you deploying the server. You only need to configure this in a multi-host cluster setup. In which case I highly recommend to use our Production Helm Chart rather than hacking the config yourself.
Hey!
I’m using Helm chart with PostgreSQL in Kubernetis and having the same issue on temporaltest-worker pod.
{"level":"error","ts":"2020-12-03T00:30:13.235Z","msg":"unable to bootstrap ringpop. retrying","service":"worker","error":"join duration of 39.662415226s exceeded max 30s","logging-call-at":"ringpop.go:114","stacktrace":"go.temporal.io/server/common/log/loggerimpl.(*loggerImpl).Error\n\t/temporal/common/log/loggerimpl/logger.go:138\ngo.temporal.io/server/common/membership.(*RingPop).bootstrap\n\t/temporal/common/membership/ringpop.go:114\ngo.temporal.io/server/common/membership.(*RingPop).Start\n\t/temporal/common/membership/ringpop.go:83\ngo.temporal.io/server/common/membership.(*ringpopMonitor).Start\n\t/temporal/common/membership/rpMonitor.go:120\ngo.temporal.io/server/common/resource.(*Impl).Start\n\t/temporal/common/resource/resourceImpl.go:370\ngo.temporal.io/server/service/worker.(*Service).Start\n\t/temporal/service/worker/service.go:177\ngo.temporal.io/server/temporal.(*Server).Start.func1\n\t/temporal/temporal/server.go:179"}
It’s surprising that server-configmap.yaml in this repository doesn’t contain any ringpop section (while banzai-charts does). Wondering how does it suppose to work?
Thank you.
I actually figured that out Sorry for bothering.