Brandon Peebles
07/31/2023, 9:14 PM/server_info
endpoint for this but I'm curious do the daemon and code location servers offer something similar? Unsure how to get ECS to think my container is healthy and keep it running. (did find this old convo from this channel but not sure if a final conclusion was ever reached)rex
08/01/2023, 4:38 PM/ping
gRPC endpoint that could be suitable. The daemon is a process, and so it doesn’t have endpoints you can reach.Brandon Peebles
08/01/2023, 4:41 PMload_from:
# Each entry here corresponds to a container that exposes a gRPC server.
- grpc_server:
host: usercode
port: 4000
location_name: "dagster_example"
Brandon Peebles
08/01/2023, 4:42 PMhost
and location_name
be referring to?rex
08/01/2023, 4:43 PMlocation_name
is just the name that will display in the Dagster UI. This can be whatever you want.
host
should be the host of your network that you have all your services running inBrandon Peebles
08/09/2023, 4:51 PMworkspace.yaml
files, but I'm still unable to connect to the code location. Currently it's getting this error:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses; last error: INTERNAL: ipv4:<ip_of_alb>:<port> Trying to connect an http1.x server".
Any ideas why it's giving this error?Jake Kara
09/08/2023, 1:45 PMJake Kara
09/08/2023, 1:45 PMJake Kara
09/08/2023, 3:59 PMssl: true
in the grpc_server entry.