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.

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

Remove default scheduler-host-address #1446

Closed
mikeee opened this issue Aug 30, 2024 · 5 comments
Closed

Remove default scheduler-host-address #1446

mikeee opened this issue Aug 30, 2024 · 5 comments
Labels
kind/bug Something isn't working stale

Comments

@mikeee
Copy link
Member

mikeee commented Aug 30, 2024

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:

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

@mikeee mikeee added the kind/bug Something isn't working label Aug 30, 2024
@artursouza
Copy link
Member

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.

@dapr-bot
Copy link
Collaborator

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

@dapr-bot dapr-bot added the stale label Oct 11, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@mikeee mikeee reopened this Oct 18, 2024
@dapr-bot dapr-bot removed the stale label Oct 18, 2024
@dapr-bot
Copy link
Collaborator

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

@dapr-bot dapr-bot added the stale label Nov 17, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

3 participants