Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
None
-
None
-
None
Description
There is some recent change that caused the application resource usage report to have a new format:
Prior the change, the format was:
YK_APP_SUMMARY: {"appID": "app-1", "submissionTime": 1712169262131, "startTime": 1712169264134, "finishTime": 1712173619983, "user": "user1", "queue": "root.queue-large", "state": "Completed", "rmID": "test-cluster", "resourceUsage": {"insttype-1":{"memory":139178200478515200,"pods":1729129,"vcore":5183062000},"insttype-2":{"memory":113789789798400,"pods":1413,"vcore":4239000}}, "preemptedResource": {}}
with the change, the new format is:
2024-04-04T00:33:08.532Z INFO core.scheduler.application.usage objects/application_summary.go:60 YK_APP_SUMMARY: {ApplicationID: app-2, SubmissionTime: 1712190615461, StartTime: 1712190617496, FinishTime: 1712190788532, User: user2, Queue: root.queue-large, State: Completed, RmID: test-cluster, ResourceUsage: TrackedResource{UNKNOWN:pods=177,UNKNOWN:vcore=354000,UNKNOWN:memory=1431454089216}, PreemptedResource: TrackedResource{}, PlaceholderResource: TrackedResource{}}
There are several incompatibilities:
1. the class name TrackedResource was not there before, now it is.
2. the instance type was outside the resource part before, not it's embedded
3. the instance type was reported correctly before the change, now it's UNKNOWN
#3 may be a different issue, but it's observed by us at the same time.
I think what should change the format back to the original one, as this is an incompatible change. What do you think wilfreds , pbacsko ,ccondit ?
Thanks.