Hello Team - Hope everyone is doing good. We are running a 3 node cluster on opensource version with docker on BMs and it crashes intermittently. Below is the logs at the time of the crash. I couldn’t gather anything better 
here. Requesting your help and let me know if you need any other information.
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“level”:“warn”,“ts”:“2020-09-25T03:22:25.803-0700”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”:“endpoint://client-868a21c9-313d-4570-99dd-43bd77d24c75/<Node_IP>:2379”,“attempt”:0,“error”:“rpc error: code = Canceled desc = context canceled”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“error”:“internal error: internal error: context canceled”,“level”:“error”,“msg”:“backend stopped working and is restarting”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down dashboardd”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down tessend”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down apid”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down keepalived”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down agentd”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down schedulerd”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down eventd”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down pipelined”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down message_bus”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down backend_id_getter”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:25 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down etcd”,“time”:“2020-09-25T03:22:25-07:00”}
Sep 25 03:22:36 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“info”,“msg”:“shutting down etcd”,“time”:“2020-09-25T03:22:36-07:00”}
Sep 25 03:22:36 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“level”:“error”,“msg”:“error starting keepalived: error initializing keepalive “ns1/client_fqdn”: rpc error: code = Canceled desc = grpc: the client connection is closing”,“time”:“2020-09-25T03:22:36-07:00”}
Sep 25 03:22:36 nodename.domain.com docker-sensugo-backend[12529]: {“component”:“backend”,“error”:“error starting keepalived: error initializing keepalive “ns1/client_fqdn”: rpc error: code = Canceled desc = grpc: the client connection is closing”,“level”:“fatal”,“msg”:“error executing sensu-backend”,“time”:“2020-09-25T03:22:36-07:00”}
=============================================================================
One more question, when I see the etcd metrics endpoint for the individual nodes, I see the sensugo agent sessions metrics is not uniform, which I believe because I have configured a VIP in the agent config. Is this expected ? And, is it advisable to configure the traffic strategy from round robin to Least connections for me to split the load uniform. Please advice/correct me if I am wrong.