Skip to content

Dont start http server in Scheduler.__init__ #4896

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

Closed
wants to merge 1 commit into from

Conversation

fjetter
Copy link
Member

@fjetter fjetter commented Jun 9, 2021

This refactors the scheduler init such that the HTTP server is only started once the server is actually up. Otherwise every init call starts an http server and binds sockets, etc.

I tried testing for leaking sockets but that's not easy. Depending on OS this requires root and even with root, I had trouble asserting this properly using psutil.

Closes #4806

@fjetter
Copy link
Member Author

fjetter commented Jun 9, 2021

This needs much more work. Ran the wrong tests locally :/

@fjetter fjetter closed this Jun 9, 2021
@mrocklin
Copy link
Member

mrocklin commented Jun 9, 2021 via email

@fjetter
Copy link
Member Author

fjetter commented Jun 9, 2021

One reason why it is in init is that we can then align security and ensure that if either scheduler comm or http server is secured, the other one must be as well. At least this is one not-trivial thing I found locally. Why the CI deadlocks immediately is beyond my understanding atm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] Warnings about used ports
2 participants