@SergeyBykov - sorry delay in response.
I have taken the latest master branch code v15.2.
I would see v1.12 version is more stable than other later versions.
Worker pod keep crashing with the below error, other 3 services pod keep running and healthy.
After applying the both PRs still context deadline error. I really don’t understood what is wrong ?
tls:
frontend:
client:
forceTLS: true
rootCaFiles:
- “##CA_CERT_FILE##”
systemWorker:
certFile: /etc/temporal/cacerts/cluster-internode.pem
keyFile: /etc/temporal/cacerts/cluster-internode.key
client:
serverName: “frontend:7233”
rootCaFiles:
- /etc/temporal/cacerts/cluster-ca-intermediate.pem
{“level”:“debug”,“ts”:“2022-03-23T07:26:00.195Z”,“msg”:“Membership heartbeat upserted successfully”,“service”:“worker”,“address”:“100.127.110.24”,“port”:6939,“hostId”:“79e70db5-aa7a-11ec-8a57-be8783a543f3”,“logging-call-at”:“rpMonitor.go:163”}
{“level”:“fatal”,“ts”:“2022-03-23T07:17:53.093Z”,“msg”:“error starting scanner”,“service”:“worker”,“error”:“context deadline exceeded”,“logging-call-at”:“service.go:436”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Fatal\n\t/temporal/common/log/zap_logger.go:150\ngo.temporal.io/server/service/worker.(*Service).startScanner\n\t/temporal/service/worker/service.go:436\ngo.temporal.io/server/service/worker.(*Service).Start\n\t/temporal/service/worker/service.go:343\ngo.temporal.io/server/service/worker.ServiceLifetimeHooks.func1.1\n\t/temporal/service/worker/fx.go:79”}