How does NSO guarantee high-availability?

[tail-f_expert]

How does NSO guarantee high-availability?

[tail-f_expert · Accepted solution]

NSO can be configured to run in HA mode: one master and several slaves. All slaves are updated at every transactional border. The slaves can be used for reading data. The slaves are hot-standby and a fail-over to a slave can be made at any time. In the clustered solution described above, each cluster node is typically a HA configuration.

[eric.n.dunn.ctr]

Is there any documentation that provides instruction on how to configure the Master and Slaves on separate servers?

I can follow the provided 'manual-ha' in the examples, but have not figured out how to configure the Master and Slave on separate servers.

[Jan Lindblad]

As far as I can tell there's nothing in the example that suggests that you should or depends on that you run both instances on the same host. On the contrary, the normal use case here would be to run on separate servers.

In what way is the trouble you see manifesting itself? If you have trouble with this (very simple, not very useful) HA setup, maybe you could try some other, e.g. the HCC package?

[eric.n.dunn.ctr]

Hi,

I took your advice and started testing tailf-hcc package.

I still do not have success and have tried multiple configurations.

I have a tac case opened.  I sent them all my logs and configuration files.

Maybe they can see why master won't connect to the slave.