-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add endpoint to get User and Groups resource usage #104
Comments
Hi, I am interested in this issue. |
Goalwe want to answer the question "How much resource is being used by a user or group? for a specific duration of time?"
Existing Resource Usage API in Yunikorn Core
These APIs return resource usage of queues in a hierarchical response. For our purpose, a similar response will not be useful because they do not consider historical resource usage. Sample Response of [
{
"userName": "user1",
"groups": {
"app2": "tester"
},
"queues":
{
"queuePath": "root",
"resourceUsage": {...},
"children": [
{
"queuePath": "root.default",
"resourceUsage": {...},
"children": [
{
"queuePath": "root.default.test",
"resourceUsage": {
"memory": 6000000000,
"vcore": 6000
},
"children": [...]
}
]
}]
}
}
] Problem with returning resource usage by queuesScenario 1: Let's say, user-a and user-b both have submitted job to the same queue. Probable Solutionresource usage for each application is stored in the Some useful columns in the
[
{
"userName": "user1",
"groups": {
"app2": "tester"
},
"applications":
[
{
"queuePath": "root.default.test",
"app_id": "app1",
"maxUsedResource": {
"memory": 6000000000,
"vcore": 6000
}
}
]
}
] Questions
|
Add a handler (and prerequisite database layer structures/code, if they don't already exist) to replicate the yunikorn-core endpoints
/ws/v1/partition/:partition/usage/users
/ws/v1/partition/:partition/usage/user/:user
/ws/v1/partition/:partition/usage/groups
/ws/v1/partition/:partition/usage/group/:group
to allow YHS users to get resource usage metrics for users and groups, at aggregate and individual levels.
The text was updated successfully, but these errors were encountered: