This document was generated from CDN thread
Created by: Aswien Behari on 28-04-2010 09:03:39 AM
Hi all,
We have been using the document “ TANDBERG Content Server Creating and managing a TCS cluster S3.3” for cluster management. In section 2 Main Features (Outbound H.323 Calls load balancing) the explanation is not clear enough for us.
What does the following means?
For added redundancy of the API functionality and to ensure that the external implementation does
not artificially create a "controller" it is up to the integrator to build
the logic around distributing the API commands among all Content Servers in
the cluster to deal with situations such as Content Server unavailability.
Doesn’t the cluster handles that? Can you guys please explain to me what this means?
Thanks in advance.
With kind regards,
Aswien
Subject: RE: Outbound H.323 Calls and API commands
Replied by: Peter Moodie on 28-04-2010 12:54:33 PM
Hi Aswien,
What this means is that when your application sends an API command to a cluster, it is recommended that it should NOT be sent to just one member of that cluster (for example, a hard-coded IP address or cluster member name). This is because if you do that, and then that particular TCS becomes unavailable for any reason, then your application will loose connection to the entire cluster.
Instead, you should make sure that your application issues API commands through the same sort of mechanism that is recommended for front-ending the cluster UI - for example a hardware load balancer, a software load balancer, or as a last resort, usinf something like DNS round-robin.
Hope that makes it a bit clearer.
Regards
Peter
