-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container resources are not passed through properly #363
Comments
Any updates on this? Have the same issue. Resources set by sparkapplication manifest just ignored. |
We haven't planned this yet. Please feel free to add any information in the comments that will help us to prioritize this (e.g. how critical it is). |
Hi Andrew, thanks for the prompt reply. For us correct resource allocation is critical as we use number of continius jobs (up to 10-20) with no so huge load (100-200m will be enough for them) but now only 1 cpu can be allocated per pod which makes our AWS bill grow faster |
Hallo Vasily, this should be fixed now. The resource settings are passed through as-is for the pods, although a rounded value is still used for the level of parallelism. |
Thanks! When you going to make next release? |
The next release is scheduled for sometime in July, but the nightly/dev versions are available already. |
Do you have docker images for nightly/dev versions? |
Confirmed. Issue is fixed. Thanks! |
Affected Stackable version
0.0.0-dev
Affected Apache Spark-on-Kubernetes version
3.5.0
Current and expected behavior
I configure
to not waste a whole core for my driver (the default is request = limit =
1
, IMHO we should lower that to250m
and1
) and get the stack running on my Laptop.However this is ignored and the driver still has
Same applies to the executor, have not checked the spark-submit Pod.
I can not fix this using podOverrides, (as spark overwrites what is in the pod-template)
Possible solution
Properly propagate resources.
Additional context
Environment
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: