Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The numeric suffix of resources causes an exception: "Invalid maximum heap size: -Xmx1000Mi" #375

Closed
tpiperatgod opened this issue May 26, 2022 · 0 comments · Fixed by #386
Closed

The numeric suffix of resources causes an exception: "Invalid maximum heap size: -Xmx1000Mi" #375

tpiperatgod opened this issue May 26, 2022 · 0 comments · Fixed by #386
Assignees
@tpiperatgod
Labels
compute/serverless
Milestone
2022-06 v0.3.0

Comments

@tpiperatgod
Copy link
Contributor

Since the Function can use spec.resources to set the size of the JVM heap, users will refer to this docs to set spec.resources.limits and spec.resources.requests.

As recommended by Kubernetes, the value suffix can be "Mi, Gi", etc., but it is invalid for Java commands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tpiperatgod tpiperatgod

Labels
compute/serverless
Projects
None yet
Milestone
2022-06 v0.3.0
Development

Successfully merging a pull request may close this issue.

fix: convert the memory value to decimal format
2 participants
@freeznet @tpiperatgod