Josh van Leeuwen
Josh van Leeuwen
@bbhxwl I think you are asking about whether Dapr Scheduler & Placement support multi-cluster (?)- no Dapr doesn't support this and should be the case that each Scheduler cluster connects...
Multiple daprds connect to the same control plane, which include scheduler and placement. https://docs.dapr.io/concepts/dapr-services/
Daprd connects to all scheduler replicas https://docs.dapr.io/concepts/dapr-services/scheduler/
This port is a gRPC endpoint, and is not expected to be communicatable from something like curl. It is also serving TLS form the Dapr trust anchor, not trusted by...
Hi @nikoraes, what SDK are you using? `failed to create actor: actor type dapr.internal.digitaltwins.dt-flows.workflow not registered"` Suggests a workflow runtime client is not connected by the application. This was a...
@nikoraes I am expecting the issue you are seeing here to have been resolved after this upgrade 🙂 This happens on start-up as the the daprd actor registration has not...
Hi @nikoraes, no I was talking about upgrading the versions, rather than moving to dapr shared. Looking at the logs you've shared, it seems like now there is a _different_...
@nikoraes based on the fact that restarting the scheduler gets things moving again I can see two possibilities- Either their is a max concurrency setting on the Dapr configuration which...
Please it not running with TLS, which should not be the case in Kubernetes. Please share the logs of placement.
@m3nax nope, looks good to me 🙂