[
https://issues.apache.org/jira/browse/IGNITE-12111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141782#comment-17141782
]
Ignite TC Bot commented on IGNITE-12111:
----------------------------------------
{panel:title=Branch: [pull/7922/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5379952&buildTypeId=IgniteTests24Java8_RunAll]
> Cluster ID and tag: properties to identify the cluster
> ------------------------------------------------------
>
> Key: IGNITE-12111
> URL: https://issues.apache.org/jira/browse/IGNITE-12111
> Project: Ignite
> Issue Type: New Feature
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> To improve cluster management capabilities two new properties of the cluster
> are introduced:
> # A unique cluster ID (may be either a random UUID or random IgniteUUID).
> Generated upon cluster start and saved to the distributed metastorage.
> Immutable. Persistent clusters must persist the value. In-memory clusters
> should keep the generated ID in memory and regenerate it upon restart.
> # Human-readable cluster tag. Generated by default to some random (but still
> meaningful) string, may be changed by user. Again survives restart in
> persistent clusters and is regenerated in in-memory clusters on every restart.
> These properties are exposed to standard APIs:
> # EVT_CLUSTER_TAG_CHANGED event generated when tag is changed by user;
> # JMX bean and control utility APIs to view ID and tag and change tag.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
