Closed AkhilTThomas closed 1 year ago
Thanks for reporting this issue, we will have a look.
Hi @AkhilTThomas, thanks for the report.
The dapr sidecar is a separate process which takes some time to start up, hence why you are seeing the 500 in the logs. If we add a delay, it will degrade some systems with faster startup of the dapr sidecar. I would suggest we change the logs to report Waiting for dapr sidecar
in case of ERR_HEALTH_NOT_READY
instead of the internal server error.
What happened?
When launching an app with sidecar the
wait_for_sidecar
API fails as the dapr healthz returns 500. However if a delay is added before calling health check it succeeds. Detailed log is attached.Operating System
Linux
What release version or branch did you use?
0.4.6
Relevant log output
Code of Conduct