[jira] [Commented] (LIVY-178) PySpark sessions crash on invalid string
[
https://issues.apache.org/jira/browse/LIVY-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910924#comment-16910924
]
Yiheng Wang commented on LIVY-178:
--
This was reported in 0.2. Maybe it has been fixed in the latest version.
> PySpark sessions crash on invalid string
>
>
> Key: LIVY-178
> URL: https://issues.apache.org/jira/browse/LIVY-178
> Project: Livy
> Issue Type: Bug
> Components: Interpreter
>Affects Versions: 0.2
> Environment: {code}
> print "\xHH"
> {code}
> will crash the session
>Reporter: Alex Man
>Assignee: Alex Man
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (LIVY-515) Livy session is idle even if spark context is unavailable
[ https://issues.apache.org/jira/browse/LIVY-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910923#comment-16910923 ] Yiheng Wang commented on LIVY-515: -- This is reported in 0.4.0. Maybe this issue has been fixed in latest version. > Livy session is idle even if spark context is unavailable > - > > Key: LIVY-515 > URL: https://issues.apache.org/jira/browse/LIVY-515 > Project: Livy > Issue Type: Bug > Components: Core >Affects Versions: 0.4.0 >Reporter: Raghavendra >Priority: Major > Attachments: AfterKillingLivy.png, BeforeKillingLivy.png, > command.history, livy-log, livyUI.png > > > When using livy in the session mode, Livy is not able to figure out if the > application master is available. > Say suppose livy was in the idle state, now for some reason the application > master died. Ideally, even the session associated with this application > master should either be terminated or should have handled this situation. > Instead, the session continues to remain in the Idle state. This is wrong. > > Steps to reproduce. > # Bring up livy in session mode(I am using 5 sessions). > # Kill the application master using "yarn application -kill " > # Now list the application in yarn "yarn application -list" you will see 4 > application master(I had 5, Killed 1 so 4) > # Now reload livy UI. You will still see 5 sessions in idle. > Attached the session logs whose application master was killed. > Attached are some images depicting the issue -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (LIVY-573) Add tests for operation logs retrieval
[ https://issues.apache.org/jira/browse/LIVY-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Gaido reassigned LIVY-573: Assignee: Yiheng Wang > Add tests for operation logs retrieval > -- > > Key: LIVY-573 > URL: https://issues.apache.org/jira/browse/LIVY-573 > Project: Livy > Issue Type: Improvement > Components: Tests, Thriftserver >Reporter: Marco Gaido >Assignee: Yiheng Wang >Priority: Trivial > Time Spent: 1h > Remaining Estimate: 0h > > Our current tests do not cover the retrieval of operation logs. We should try > and add coverage for it if possible. -- This message was sent by Atlassian Jira (v8.3.2#803003)
