manirajv06 opened a new pull request, #740: URL: https://github.com/apache/yunikorn-core/pull/740
### What is this PR for? 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.. ### What type of PR is it? * [ ] - Improvement ### Todos * [ ] - Task ### What is the Jira issue? https://issues.apache.org/jira/browse/YUNIKORN-2204 ### How should this be tested? Existing unit tests would cover this. ### Screenshots (if appropriate) ### Questions: * [ ] - The licenses files need update. * [ ] - There is breaking changes for older versions. * [ ] - It needs documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
