shanyu zhao created LIVY-505:
Summary: sparkR.session failed with "invalid jobj 1" error in
Spark 2.3
Key: LIVY-505
URL: https://issues.apache.org/jira/browse/LIVY-505
Project: Livy
Issue Type:
[
https://issues.apache.org/jira/browse/LIVY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687299#comment-16687299
]
shanyu zhao commented on LIVY-231:
--
Any update for this feature? Or should we implement an active-standby
[
https://issues.apache.org/jira/browse/LIVY-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704312#comment-16704312
]
shanyu zhao commented on LIVY-266:
--
[~tc0312] are you saying that all the requests are actually using
[
https://issues.apache.org/jira/browse/LIVY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shanyu zhao updated LIVY-576:
-
Attachment: LIVY-576.patch
> Unknown YARN state RUNNING for app with final status SUCCEEDED
>
[
https://issues.apache.org/jira/browse/LIVY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shanyu zhao updated LIVY-576:
-
Summary: Unknown YARN state RUNNING for app with final status SUCCEEDED
(was: Unknown YARN state RUNNING
shanyu zhao created LIVY-576:
Summary: Unknown YARN state RUNNING FOR app with final status
SUCCEEDED
Key: LIVY-576
URL: https://issues.apache.org/jira/browse/LIVY-576
Project: Livy
Issue Type:
[
https://issues.apache.org/jira/browse/LIVY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803315#comment-16803315
]
shanyu zhao commented on LIVY-505:
--
Root cause:
SparkR uses SparkR env variable ".sparkRjsc" as a
[
https://issues.apache.org/jira/browse/LIVY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shanyu zhao updated LIVY-505:
-
Attachment: LIVY-505.patch
> sparkR.session failed with "invalid jobj 1" error in Spark 2.3
>
[
https://issues.apache.org/jira/browse/LIVY-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780032#comment-16780032
]
shanyu zhao commented on LIVY-547:
--
[~Jassy] are you still working on this issue?
> Livy kills session
shanyu zhao created LIVY-617:
Summary: Livy session leak on Yarn when creating session
duplicated names
Key: LIVY-617
URL: https://issues.apache.org/jira/browse/LIVY-617
Project: Livy
Issue
[
https://issues.apache.org/jira/browse/LIVY-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897494#comment-16897494
]
shanyu zhao commented on LIVY-547:
--
Created new PR and added new configuration to change the behavior of
[
https://issues.apache.org/jira/browse/LIVY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043920#comment-17043920
]
shanyu zhao commented on LIVY-576:
--
Thanks [~andrasbeni], yes LIVY-642 is basically a duplicate of this
shanyu zhao created LIVY-750:
Summary: Livy uploads local pyspark archives to Yarn distributed
cache
Key: LIVY-750
URL: https://issues.apache.org/jira/browse/LIVY-750
Project: Livy
Issue Type:
shanyu zhao created LIVY-749:
Summary: Datanucleus jars are uploaded to hdfs unnecessarily when
starting a livy session
Key: LIVY-749
URL: https://issues.apache.org/jira/browse/LIVY-749
Project: Livy
[
https://issues.apache.org/jira/browse/LIVY-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shanyu zhao updated LIVY-749:
-
Issue Type: Bug (was: New Feature)
> Datanucleus jars are uploaded to hdfs unnecessarily when starting a
[
https://issues.apache.org/jira/browse/LIVY-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010965#comment-17010965
]
shanyu zhao commented on LIVY-718:
--
LIVY-11 aims at active-standby HA, user should be able to choose
[
https://issues.apache.org/jira/browse/LIVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shanyu zhao updated LIVY-750:
-
Description:
On Livy Server, even if we set pyspark archives to use local files:
{code:bash}
export
17 matches
Mail list logo
