Hi folks! We're using the SpiceDB
# spicedb
s
Hi folks! We're using the SpiceDB operator to deploy our SpiceDB cluster. We noticed that whenever spicedb cluster pod shuts down and a new one spins up, some of our grpc calls start failing (for around a minute) with one of two errors: -
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <address>:50051: connect: connection refused”
-
rpc error: code = DeadlineExceeded desc = received context error while waiting for new LB policy update: context deadline exceeded
Is there a way we can handle this more gracefully?
48 Views