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 2025/11/10 17:13:03 UTC
[jira] [Updated] (LIVY-435) Livy forces driver/executor core count to an integer instead of a float
[ https://issues.apache.org/jira/browse/LIVY-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyorgy Gal updated LIVY-435:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If you feel this is moved out inappropriately, feel free to provide justification and reset the Fix Version to 0.9.0.
> Livy forces driver/executor core count to an integer instead of a float
> -----------------------------------------------------------------------
>
> Key: LIVY-435
> URL: https://issues.apache.org/jira/browse/LIVY-435
> Project: Livy
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.4.0
> Reporter: Noah Kantrowitz
> Priority: Minor
> Fix For: 0.10.0
>
>
> When creating a session or batch, the cores count is required to be an integer while Spark itself allows floating point values. This has mattered for some of my local testing with Kubernetes as it will refuse to schedule executors if they are requesting more CPU power than is actually available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)