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 2020/01/10 13:49:00 UTC

[jira] [Assigned] (DLAB-539) [KeyCloak]: Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.2.1) can't be established on Jupyter

     [ https://issues.apache.org/jira/browse/DLAB-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vira Vitanska reassigned DLAB-539:
----------------------------------

    Assignee: Mykola Bodnar  (was: Adams Disturber)

> [KeyCloak]: Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.2.1) can't be established on Jupyter
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DLAB-539
>                 URL: https://issues.apache.org/jira/browse/DLAB-539
>             Project: Apache DLab
>          Issue Type: Bug
>          Components: DLab Old
>            Reporter: Anna Orlovska
>            Assignee: Mykola Bodnar
>            Priority: Major
>              Labels: 2.3_old, AWS, DevOps, Known_issues(release2.2)
>             Fix For: v.2.3
>
>         Attachments: EMR519.png, Status.png
>
>
> *Preconditions:*
>  EMR v.5.19 for Jupyter is created and running.
> *Steps to reproduce:*
>  # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running
> *Actual result:*
>  EMR kernel is NOT started successfully
> *Expected result:*
>  EMR kernel is started successfully
>  
> EMR kernel is not started onle for EMR v.5.19. 
> And on the other Jupyter for EMR[5.19] it is the same glitch with starting.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org