[ https://issues.apache.org/jira/browse/YUNIKORN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikandan R resolved YUNIKORN-2204. ------------------------------------ Resolution: Fixed > Use ask unique id for allocation > -------------------------------- > > Key: YUNIKORN-2204 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2204 > Project: Apache YuniKorn > Issue Type: Improvement > Reporter: Manikandan R > Assignee: Manikandan R > Priority: Major > Labels: pull-request-available, release-notes > > 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.. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org