search

nebari-dev / nebari

🪴 Nebari - your open source data science platform
https://nebari.dev
BSD 3-Clause "New" or "Revised" License
266 stars 88 forks source link

[BUG] - Increase idle culler defaults to 30 min #2508

Open Adam-D-Lewis opened 2 weeks ago

Adam-D-Lewis commented 2 weeks ago

Describe the bug

It's frustrating for users to have the kernel die frequently. Although this can be overridden in the nebari config I think it's worthwhile increasing the default settings to 30 minutes rather than 15. This has been a problem for users processing large data sets as well as for local LLM usage where the 15 minute idle culler is frustrating.

BTW, here is how to change the settings in the Nebari config.

jupyterlab:
  idle_culler:
    terminal_cull_inactive_timeout: 30
    kernel_cull_idle_timeout: 30
    server_shutdown_no_activity_timeout: 30

More docs are at https://www.nebari.dev/docs/how-tos/idle-culling/

Expected behavior

see aboveo

OS and architecture in which you are running Nebari

Linux x86-64

How to Reproduce the problem?

see above

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

Adam-D-Lewis commented 2 weeks ago

had another user say this was driving him nuts lately as well

viniciusdc commented 1 week ago

increasing the kernel timeout limit to 30min would lead the pod overall timeout limit went to 45min instead of the current 30min. I also think that's a good re-arrangement. I just wonder if we would like to increase the others (e.g terminal) as well.