Skip to content

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

Open
@pruthvidhodda

Description

@pruthvidhodda

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1enhancementNew feature or requestpinneddapr-bot exemption

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions