Assume there is a multi-process application working as a NIProvider. It connects to one of two ADH-s configured to accept connection from the application. Please note that these two ADH-s do not work in a hot standby for NIP service. NIP on ADH-s is configured for source aggregation and communication is on TCP. It's not multicast.
The multi-process application has several instances and each one at any point in time may be streaming updates to one of the ADH-s. However at a given time, only one instance is streaming updates for a given unique RIC, there is no overlapping over time.
The application is normally connected to the primary ADH, but if this one goes down then it may connect to the second ADH. When that happens, it will start streaming RICs updates to the secondary ADH. After some time a task of streaming updates for a given RIC may go back to another instance that is connected to primary ADH. Question:
How should the instance connected to secondary ADH "end" the stream of updates such that there is only one open stream for a given RIC among the ADH-s?
In other words goal is to have a given RIC only opened on one ADH. If that is not done, then ADS-s are confused: one of them might get the stream from secondary ADH (wrong, the stream is not being updated there anymore), but another one might reach to a primary ADH (good).