wilfred-s commented on pull request #372: URL: https://github.com/apache/incubator-yunikorn-core/pull/372#issuecomment-1043826964
The solution works but would break when there is more than one RM. We need to prevent that. We need to move the registration of the data into the `ClusterContext.processRMRegistrationEvent()` and track it for that specific RM. Since a RM can have more than one partition we should not store it in the partition (partition map uses the normalised name which is "[RM]partition"). A new field in the `ClusterContext` struct: ```rmInfos map[string]*rmInformation``` The _rmInformation_ is a simple struct. It should contain all the data from the build info (simple map). The registration or start date should be set when the object is created. We can add more details to that in the next steps. We do need to make sure that the fields are not ambiguous: Date could be anything, it is much clearer to use buildDate Access to the _rmInformation_ would go through the cluster like the partition map cloning. For making the data available on rest we should use a similar object to the rmInformation object in the dao. I think we need to expose it as part of the cluster details and not as a separate endpoint as we could have multiple RMs etc. -- 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]
