You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scheduler streaming client should not be initialised by default with the run command following changes in 1.14.1. This makes it consistent with the multi-app run for example.
Actual Behavior
A scheduler client connection is initialised and failing to connect.
Steps to Reproduce the Problem
Command:
dapr run --app-id testapp
Result:
Scheduler client initialised with localhost:50006 and failing to connect repeatedly
Release Note
RELEASE NOTE: UPDATE Scheduler client is no longer initialised by default
The text was updated successfully, but these errors were encountered:
That is an interesting one because connecting to scheduler by default was done because it is needed for Jobs API to work, even as an alpha feature. Maybe, we change runtime so it does not fail if cannot connect to scheduler? It would also mean that Jobs API is not available to those instances either.
Expected Behavior
The scheduler streaming client should not be initialised by default with the
run
command following changes in 1.14.1. This makes it consistent with the multi-app run for example.Actual Behavior
A scheduler client connection is initialised and failing to connect.
Steps to Reproduce the Problem
Command:
Result:
Scheduler client initialised with
localhost:50006
and failing to connect repeatedlyRelease Note
RELEASE NOTE: UPDATE Scheduler client is no longer initialised by default
The text was updated successfully, but these errors were encountered: