[BP 6.6.3] On rebalanced out node on remote link, target cluster details can be lost

For remote links, analytics monitors and accommodates target cluster topology changes, by monitoring a streaming endpoint /pools/default/nodeServicesStreaming on one of the nodes in the target cluster. Should the node analytics is monitoring against itself get rebalanced out, analytics may connect back to the rebalanced out node not realizing that it has left the cluster. Based on the topology information it receives from the cluster-less node, it will wipe out the valid topology information in the remote link, leaving the link in a broken state:

• additional topology changes will not be realized
• should the link disconnect, and is reconnected:
  • it will believe that the shadowed buckets have been dropped, causing all analytics collections on that remote link to truncate
  • other than to truncate the analytics collections, the link will to connect
• the link will continue to not be usable until either:
  • the rebalanced out node happens to be added back to the cluster
  • the link is ALTERed or DROPped+re-CREATEd