You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/21 12:25:00 UTC
[jira] [Updated] (DLAB-444) [Spark Standalone Cluster]: Schedule by
inactivity does not work for cluster if it is more than one spark clusters
on the same notebook
[ https://issues.apache.org/jira/browse/DLAB-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated DLAB-444:
--------------------------------
Labels: Back-end pull-request-available (was: Back-end)
> [Spark Standalone Cluster]: Schedule by inactivity does not work for cluster if it is more than one spark clusters on the same notebook
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DLAB-444
> URL: https://issues.apache.org/jira/browse/DLAB-444
> Project: Apache DLab
> Issue Type: Bug
> Reporter: Vira Vitanska
> Assignee: Bohdan Hliva
> Priority: Major
> Labels: Back-end, pull-request-available
> Fix For: v.2.2
>
>
> *Preconditions:*
> 1. Two Spark Standalone clusters are created on the same notebook
> *Steps to reproduce:*
> 1. Set schedule by inactivity for the second created spak cluster
> *Actual result:*
> Schedule by inactivity does not work for the second created spak cluster (spark cluster is running after passing inactivity time)
> *Expected rsult:*
> Schedule by inactivity works for the second created spak cluster (spark cluster is stopped after passing inactivity time)
--
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