[
https://issues.apache.org/jira/browse/YARN-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878316#comment-16878316
]
hunshenshi commented on YARN-9663:
----------------------------------
Just add the clusterId of the resourcemanager in applicationId, it happens in
rm, can't expose to client. Client do as before.
It will fix from the root.
Default applicationId is application_timestamp_xxx1, I will add `clusterId`
after `application`, then the applicationId will be
application_{color:#FF0000}clusterId{color}_timestamp_xxx1.
> ApplicationID may be duplicated in YARN Federation
> --------------------------------------------------
>
> Key: YARN-9663
> URL: https://issues.apache.org/jira/browse/YARN-9663
> Project: Hadoop YARN
> Issue Type: Bug
> Components: federation, yarn
> Reporter: hunshenshi
> Assignee: hunshenshi
> Priority: Major
>
> ApplicationId represents the globally unique identifier for an application.
> The globally unique nature of the identifier is achieved by using the cluster
> timestamp. i.e. start-time of the ResourceManager along with a monotonically
> increasing counter for the application.
> But in yarn federation, the applicationId will be duplicated if the timestamp
> of subClusters is same.
> Shall we add clusterId in applicationId, like
> application_cluseterId_timestamp_xxx1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
