-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAPR Sidecar fails as Pub Sub container takes time to initiate #4170
Comments
Looks like the same issue as #2484 (comment). There's no real workaround if the dapr component isn't resilient. I'm not sure if you can configure retries. |
Sadly there is no way to configure any type of resiliency (in the init) for dapr components right now. There is the v1.14 release planning where the component resiliency is mentioned as "Not prioritized", so i am not getting my hopes up. @spicycoder i don't think there is much we can do besides making sure rabbitmq is already up and running before starting the AppHost. I also tried your repo @davidfowl WaitForDependenciesAspire but the sidecar starts regardless of what you configure (works great for the projects / containers though). In theory im guessing you could try to start the dapr sidecar with custom args inside a container and then set the WaitFor like: |
Yea, there's no way to get a handle on the side car. I think if we exposed the sidecar resource it would be possible to use WaitFor |
Any solutions to above? |
We're adding the ability to wait for resources to be health in a first class way. |
I have an Aspire project, with 2 Web API Projects
My AppHost's
Program.cs
looks likeAnd
components/pubsub.yaml
looks likeWhen I disable the statement from Aspire, to spin up an instance of RabbitMQ and use
docker run
instead, everything works just fineBut when I use Aspire to spin up an instance of RabbitMQ, with same setup (5672, 15672, guest\guest), the DAPR sidecars fail (both Publisher & Subscriber)
Error Message
Are there any known workaround?
Thanks
The text was updated successfully, but these errors were encountered: