Kbase 19245: SonicMQ: Can a Cluster Run Without a Config Server?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/7/2001 |
|
SUMMARY:
This solution applies to SonicMQ 2000.x and 3.x. It explains the role
of the configuration server in a cluster, and what happens if the
configuration server is brought down.
EXPLANATION:
In each cluster, there is one and only one configuration server. The
configuration server provides a central point for maintainenance of
the cluster configuration (what brokers are members of the cluster),
and the security information for the cluster.
If the configuration server goes down, all brokers in the cluster that
are still running continue to work and they can continue to accept new
connections.
There are only three things you cannot do while the configuration
server is down:
- Other brokers that are not already running can be started, but
they cannot accept connections until they are able to connect
to the configuration server after it comes back up.
- You cannot administer the security database
(users/groups/ACLs/message protection) because it is maintained
by the configuration server. The other brokers continue to
enforce security according to the state of the database at the
time the configuration server went down.
- Brokers cannot be added or removed from the cluster.
A failure of the configuration server, then, is only a problem if it
is going to be down for an extended period of time and one of the
above administrative tasks must be done during that time.
References to Written Documentation:
SonicMQ Installation and Administration Guide,
Chapter 2, "Administration Concepts"
SonicMQ 3.x Deployment Guide