Type of change
Please provide link to gitlab issue or ADR(Architecture Decision Record) N/A
Does this introduce a change in the core logic?
Does this introduce a change in the cloud provider implementation, if so which cloud?
Does this introduce a breaking change?
What is the current behavior?
OqmSubscriberManager (see code from line 103) checks for the presence (and creates, if not) a
register-subscriber-control topic on the broker of the first tenant it comes across in order (the list of which it reads from the Partition Service). At the same time, the order of sorting the list of tenants by the Partition service is not guaranteed, which can lead to the fact that when re-creating or restarting the Notification instance, the check for the presence and creation of the topic will occur on different brokers, which will lead to duplication of the topic, confusion and non-receipt of messages, published in the Register topic by the service.
What is the new/expected behavior?
It is necessary to change the algorithm in order to: create topic replicas on all brokers and subscribe to them on all. Pseudo-code of the target architecture and algorithm:
all tenants --> all brokers (number <= number of tenants) --> 1 topic per broker --> 1 subscription per topic --> 1 subscriber per subscription per Notification Service instance
Have you added/updated Unit Tests and Integration Tests?
Any other useful information
This change has been initiated by the EPAM JIRA GONRG-4681
This change has a paired change in the Notification service that is reflected in the tickets:
- EPAM JIRA GONRG-4680 - Fix OqmSubscriberManager (topics creation algorithm)
- OSDU MR register!213 (merged)