[OAK-3672] discovery-lite should not set (cluster)Id for tarMk and mongoMk (was: SegmentDiscoveryLiteService does not persist clusterView.id)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.10
• Fix Version/s: 1.3.15, 1.4
• Component/s: segmentmk
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 24/Nov/15 08:45
• Updated: 26/Sep/19 11:40
• Resolved: 01/Feb/16 16:23

Description

The discovery-lite-descriptor introduced with OAK-2844 has a property id that uniquely and persistently identifies a cluster. However, the SegmentDiscoveryLiteService creates this id upon each instance restart (by setting runtimeClusterId).

This should be fixed to have this id persisted somehow.

Note that the consequences of this id changing upon each restart is that the corresponding presumed-to-be-persistent ClusterView.id of the discovery.oak will also change upon restart. Which is a violation of the discovery API and upper level applications might thus misbehave in this case.

Issue Links

• is blocked by: SLING-5458 support discovery-lite's id==null (by managing the id in discovery.oak)
• is related to: SLING-3164 Clarify ClusterView.getId (was: Clarify and deprecate ClusterView.getId)
• is related to: SLING-3195 Provide a property to uniquely identify a Cluster
• is related to: OAK-3529 NodeStore API should expose an Instance ID