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

How does the Fornax Science Console decide when to cull servers? #18

Open
vandesai1 opened this issue Apr 12, 2024 · 1 comment
Open
Labels
FAQ entry Questions to include in the FAQ part of the documentation

Comments

@vandesai1
Copy link
Contributor

The Fornax Science Console will cull servers after a user is inactive for a certain amount of time. Add how long.

@bsipocz bsipocz added the FAQ entry Questions to include in the FAQ part of the documentation label Apr 15, 2024
@jkrick
Copy link
Collaborator

jkrick commented Apr 22, 2024

There is a 1 hour default timeout on the system.

More specific questions from a slack thread with @troyraen and @sawdog

  1. What event(s) starts the timer for the 1 hour cull timeout?
  2. Is there any guaranteed (or reasonably expected) minimum amount of time that the user’s computer can be disconnected from the session/server before the server is subject to being shut down?
  3. Is there any requirement for the human user to be interacting with the session (typing or clicking), or is it enough for the computer to simply maintain a connection?
  4. Does it matter at all how “active” the actual code is? If so, does this have to do with percentage of time it’s using a CPU vs just waiting for data to come in, some threshold on the load average, and/or something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FAQ entry Questions to include in the FAQ part of the documentation
Projects
None yet
Development

No branches or pull requests

3 participants