[
https://issues.apache.org/jira/browse/LIVY-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868571#comment-17868571
]
Asif Khatri edited comment on LIVY-1007 at 7/25/24 6:17 AM:
------------------------------------------------------------
A PR
[https://github.com/apache/incubator-livy/pull/453|https://github.com/apache/incubator-livy/pull/451]
has been submitted.
was (Author: JIRAUSER298707):
A PR [https://github.com/apache/incubator-livy/pull/451] has been submitted.
> Livy should not spawn one thread per job to track the job on Kubernetes
> -----------------------------------------------------------------------
>
> Key: LIVY-1007
> URL: https://issues.apache.org/jira/browse/LIVY-1007
> Project: Livy
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.9.0
> Reporter: Asif Khatri
> Assignee: Asif Khatri
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SparkKubernetesApp spawns a new thread for each application.
> The similar behaviour is observed for Yarn in LIVY-336. This process can be
> improved in a few ways to use less resources, particularly threads, and to
> shorten the latency. Some of the improvements are straightforward.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
