[YUNIKORN-1233] REST api shows negative request time for some allocations

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: core - common
• Labels: pull-request-available
• Target Version: 1.1.0
• Assignee: Peter Bacsko
• Reporter: Wilfred Spiegelenburg
• Created: 09/Jun/22 01:17
• Updated: 13/Sep/22 14:31
• Resolved: 28/Jun/22 03:06

Description

In a dump taken from a install after 1.0 we show negative requestTime entries for a small set of pods:

{
 "allocationKey": "0c381096-2ec2-45e3-ac5f-29b4bfdd82b2",
 "allocationTags": {
   ...
   "kubernetes.io/label/disableStateAware": "true",
   "kubernetes.io/label/queue": "root.default",
   "kubernetes.io/meta/namespace": "default",
  ...
   "yunikorn.apache.org/requiredNode": "ip-172-31-214-45.ec2.internal"
 },
 "requestTime": -6795364578871345152,
 "allocationTime": 1654635352762302689,
 "allocationDelay": 8449999931633647841,
 "uuid": "0c381096-2ec2-45e3-ac5f-29b4bfdd82b2",
 "resource": {
   "memory": 52428800,
   "vcore": 50
 },
 "priority": "0",
 "queueName": "",
 "nodeId": "ip-172-31-214-45.ec2.internal",
 "applicationId": "yunikorn-default-autogen",
 "partition": "default",
 "placeholder": false,
 "placeholderUsed": false,
 "taskGroupName": ""
},

Could be related to the fact that they are daemonset pods as they have the tag "yunikorn.apache.org/requiredNode" set

Issue Links

• links to: GitHub Pull Request #419
• links to: GitHub Pull Request #436