Security

Now I have configure VIP between the 2 nodes and my publisher failed and the subscriber became publisher but when the old publisher returned back online it remain subscriber? What causes this issue

This is as expected.  Please see these steps to re-join a failed publisher to the cluster. 

 

1. Original Publisher becomes reachable. A message is shown to the logged in user:



Suppose a VIP is configured between Original publisher and standby publisher/other subscriber nodes, with Primary node as Original Publisher, then VIP is not released to this Node.

2. Drop the subscriber nodes (Remove VIP and Standby Publisher settings if configured for that subscriber node). This takes few seconds for each of the node.  Ex: It takes nearly 20sec (in our test bed.. may be a max of 1min) for each of the nodes to get dropped. We should see the following error as well "ERROR - A.A.A.A: - Ignore drop node request from unknown publisher".

NOTE: Drop subscriber will not work if there are warnings, while dropping nodes, that are participating in Standby publisher operation or any VIP config. Please remove the same and perform Drop subscriber..

3. Refresh the Original publisher after dropping the subscriber nodes, and revisit Server Configuration screen [Administration » Server Manager » Server Configuration] to join this node to the cluster. Make subscriber operation starts here.

4. Original publisher is added back to the cluster as subscriber.

 

Thank you for your replayI know that  but my issue is to make thr faild publisher became publishr again when it is back online (Automatically) can I achive this?

This is not possible today