You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (JIRA)" <ji...@apache.org> on 2018/12/19 11:28:00 UTC
[jira] [Created] (DLAB-112) [Scheduler on idle]: Ability to
configure scheduler for resources stopping/termination on exceeding idle
time
Vira Vitanska created DLAB-112:
----------------------------------
Summary: [Scheduler on idle]: Ability to configure scheduler for resources stopping/termination on exceeding idle time
Key: DLAB-112
URL: https://issues.apache.org/jira/browse/DLAB-112
Project: Apache DLab
Issue Type: Improvement
Reporter: Vira Vitanska
Assignee: Bohdan Hliva
Fix For: 2.1 release
As a user I want to have a scheduler for Clusters to be stopped (Spark) or terminated (EMR) after XXX minutes of inactivity, so that I can reduce charges during non-working period with computational resources.
*Acceptance criteria:*
*1.* it should be default option
*2.* radio button should be on scheduler dialog which has this option checked and set to 120 minutes
*2.1.* in case it was configured to 120 min and on 119 minute some activity started we do not stop/terminate anything. BUT postpone stopping/termination for next 120 min
*3.* it should NOT be two schedulers at the same time (it should be configured by pattern and inactivity one)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org