Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle the logic to retry until grpc port is assigned to daprd #14

Open
pruthvidhodda opened this issue May 12, 2020 · 4 comments · May be fixed by #167
Open

Handle the logic to retry until grpc port is assigned to daprd #14

pruthvidhodda opened this issue May 12, 2020 · 4 comments · May be fixed by #167
Labels
enhancement New feature or request P1 pinned dapr-bot exemption
Milestone
0.17.0

Comments

@pruthvidhodda
Copy link
Contributor

Right now we have to introduce some delay in clients so that a grpc port is assigned to daprd before the client tries to make a connection. The logic to handle this issue needs to be handled in the sdk instead.

Logs for this issue when delay is not introduced in client:

$ dapr run --app-id=rustapp --grpc-port 3500 cargo run -- --example client
ℹ️  Starting Dapr with id rustapp. HTTP Port: 38035. gRPC Port: 3500

== APP == Error: TransportError
@dwhiteddsoft
Copy link
Contributor

On a R-Pi4. I have bumped this to 5 secs and still get the error:
== APP == Compiling dapr v0.6.0 (/home/pi/dapr-throughput/rust-sdk)
== APP == Finished dev [unoptimized + debuginfo] target(s) in 21.27s
== APP == Running target/debug/examples/publisher
== APP == Error: TransportError

Thoughts? Maybe slower Pi I should increase?

@NickLarsenNZ
Copy link
Contributor

Perhaps it needs to retry with backoff rather than just delay for an arbitrary amount of time.

I think the connection also needs to retry when dapr is restarted. I noticed a problem where my app would no longer connect back to dapr and I would have to restart it.

@mikeee mikeee added the P1 label Mar 20, 2024
@mikeee mikeee added this to the 1.14 milestone Mar 20, 2024
@mikeee mikeee added the enhancement New feature or request label Mar 20, 2024
@mikeee
Copy link
Member

mikeee commented Mar 27, 2024

Implement a resiliency strategy based off:
dapr/proposals#36

@mikeee mikeee linked a pull request Apr 18, 2024 that will close this issue
Draft
15 tasks
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted) or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label May 26, 2024
@mikeee mikeee added pinned dapr-bot exemption and removed stale labels May 26, 2024
@mikeee mikeee modified the milestones: 1.14, 1.15 Jul 23, 2024
@mikeee mikeee modified the milestones: 0.16.0, 0.17.0 Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request P1 pinned dapr-bot exemption
Projects
None yet
Milestone
0.17.0
Development

Successfully merging a pull request may close this issue.

Implement SDK resiliency mikeee/dapr_rust-sdk
4 participants
@dwhiteddsoft @NickLarsenNZ @mikeee @pruthvidhodda