Skip to content

Conversation

@mivanov1988
Copy link
Contributor

Why
Currently, we can configure data job CPU only in milicores.

What
Added an ability to provide cpu resources in either milicores or cores. Also, switched the database CPU unit to cores as it used to be.

Testing done:
Unit tests

Signed-off-by: Miroslav Ivanov [email protected]

Copy link
Collaborator

@dakodakov dakodakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mivanov1988 mivanov1988 enabled auto-merge (squash) February 14, 2024 12:35
Why
Currenlty, we can configure data job cpu only in milicores.

What
Added an ability to provide cpu resources in either milicores or cores.
Also, swithced the database cpu unit to cores as it used to be.

Testing done:
Unit tests

Signed-off-by: Miroslav Ivanov [email protected]
@mivanov1988 mivanov1988 force-pushed the person/miroslav/fix-deployment-cpu-conversion branch from 80f384b to d7a4605 Compare February 14, 2024 12:53
@mivanov1988 mivanov1988 merged commit 459d6fc into main Feb 14, 2024
@mivanov1988 mivanov1988 deleted the person/miroslav/fix-deployment-cpu-conversion branch February 14, 2024 13:35
@@ -0,0 +1,5 @@
distributionBase=GRADLE_USER_HOME
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are the gradle jar and properties in source controL? I think those are dynamically downloaded on demand when needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants