[YUNIKORN-2204] Use ask unique id for allocation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Labels: pull-request-available release-notes
• Target Version: 1.5.0
• Assignee: Manikandan R
• Reporter: Manikandan R
• Created: 28/Nov/23 14:35
• Updated: 20/Mar/24 14:32
• Resolved: 30/Nov/23 09:53

Description

As of now, every allocation has its own generated unique id using uuid(). Ask has its own unique id (reused from pod uuid propagated through task object). Because of this nature, difficult to map these id's while troubleshooting any issues through logs. Proposal is to re use the ask unique id itself even for Allocation too. Since there could be ask repeats, to avoid the duplicates, suffixing unique number to the ask unique id would end up in having  unique Allocation id for every ask repeat. This suffix starts with 0 and keeps increasing by 1 for every repeat. For example, If ask key is "alloc-1", then allocation unique id would be "alloc-1-0", "alloc-1-1", so on..

Issue Links

• split to: YUNIKORN-2211 Replace Allocation uuid with allocationID
• Testing discovered: YUNIKORN-2213 Handle Allocation allocation id during recovery properly
• links to: GitHub Pull Request #111
• links to: GitHub Pull Request #740