Closed xieus closed 3 years ago
@VanderChen @chenpiaoping Based on discussion in open-source meeting, we will need to break down the task into three parts: (1) Add two new fields on web entity (NodeInfo) and UTs change (2) Node Metadata Manager => DPM (async call) and new API in DPM for node registration (3) Fallback mechanism: DPM to retrieve missing data from NMM in case of cache miss
Addressed by PR #532
Context
The DPM pulsar client needs two mappings in the following to enable message multicast, one is group topic to host ip mapping, and the other is multicast topic to group topic mapping.
The mappings are currently stored as configurations in application.properties. For actual production deployment, this solution will not sustain due to the large number of production nodes.
Request
Think of a long-term solution to support production grade deployment. One possibility to store the mapping in node metadata manager, as this is a host-level resource.