Are there any known latency ranges that must be satisfied for NAS & NATS when DMA servers are on a global network?
What are the options and how can these affect synchronizations across the DMS?
Is stand-alone NATS node config faster than a Clustered NATS?
Which config can be lighter on SLNet.exe?
E.g. Let's say I'm evaluating a DMS cluster consisting of a DMA1 in EU and a DMA2 in the US:
when I create a new "view" on DMA1, how long am I expected to wait before I can see the same view (or element) when connecting to DMA2?
What are the options to minimize the cluster synchronization in a scenario like this, involving intercontinental link delay?
I'm assuming the stand-alone NATS node config you're mentioning is forcing the NATS configuration in a DMA cluster to not be clustered.
This is not a supported configuration and was only temporarily used to quickly get customer DMAs up and running again, after which a proper configuration has to be set up.
A stand-alone NATS configuration cannot communicate with other nodes of the DMA which makes many features not function correctly.
Hence this type of configuration should never be put in production.
So a clustered config is required. We don't however have tests to determine a specific cutoff latency at which point NATS will stop functioning reliably.
We are however in the process of implementing a new project which will decouple the NATS management from DataMiner, which will make it easier to update, maintain and provide new features.
One of those features is support for super-cluster and leafnodes, which are things provided by NATS to optimize the connectivity in a geographically distributed cluster.
We currently have no ETA for the release of this new project since there are many hurdles yet to overcome.
I hope this answers all your questions