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 2019/05/21 07:48:00 UTC
[jira] [Updated] (DLAB-334) [AWS][GCP][RStudio]: Sometimes cluster
termination/RStudio stoping with related clusrter fails
[ https://issues.apache.org/jira/browse/DLAB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vira Vitanska updated DLAB-334:
-------------------------------
Fix Version/s: v.2.3
> [AWS][GCP][RStudio]: Sometimes cluster termination/RStudio stoping with related clusrter fails
> ----------------------------------------------------------------------------------------------
>
> Key: DLAB-334
> URL: https://issues.apache.org/jira/browse/DLAB-334
> Project: Apache DLab
> Issue Type: Bug
> Components: AWS, GCP
> Environment: AWS, GCP
> RStudio
> Reporter: Vira Vitanska
> Assignee: Demyan Mysakovets
> Priority: Minor
> Labels: Debian, DevOps, GCP_demo, RedHat
> Fix For: v.2.1, v.2.2, v.2.3
>
> Attachments: AWS console.PNG, EMR termination.PNG
>
>
> *Preconditions:*
> 1. EMR or Spark standalone cluster is created
> *Steps to reproduce:*
> 1. terminate EMR or Spark standalone cluster
> *Actual result:*
> 1. EMR/Saprk standalone termination fails on DLab UI
> 2. EMR/Saprk is terminated on AWS console
> !EMR termination.PNG!
> !AWS console.PNG!
>
> *Expected result:*
> 1. EMR/Saprk standalone termination is successful on DLab UI
> 2. EMR/Saprk is terminated on AWS console
> ***Why command is done for jupyter s*udo: rm -rf /home/dlab-user/.local/share/jupyter/kernels/*_vit_2112-vira_vitanska-des-rs-519spo-cust-5ca34*?
> Also the bug was reproduced if stop RStudio with related clusters (GCP)
--
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