You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Gyorgy Gal (Jira)" <ji...@apache.org> on 2024/08/12 12:26:00 UTC

[jira] [Resolved] (LIVY-1007) Livy should not spawn one thread per job to track the job on Kubernetes

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

Gyorgy Gal resolved LIVY-1007.
------------------------------
    Fix Version/s: 0.9.0
       Resolution: Fixed

> 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
>             Fix For: 0.9.0
>
>          Time Spent: 0.5h
>  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)