Open topic with navigation
NuoDB Professional Services can provide a balancer plugin that you can use to make a broker passive. A passive broker remains in the domain but it rejects any SQL client connections.
The main class in the
ActivePassive runnable JAR file is
com.nuodb.activepassive.Keeper. This JAR file:
To install the
ActivePassive balancer plugin in a broker:
/opt/nuodb/etc/default.properties to specify the
ActivePassive plugin as part of the setting of the
balancer property. For example:
balancer = com.nuodb.activepassive.Gate,ChainableTagBalancer,ChainableRegionBalancer
/etc/nuodb/jvm-options to allow remote JMX management:
NUODB_AGENT_JAVA_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=19999 -Dcom.sun.management.jmxremote.authenticate=false"
Restart the broker:
sudo service nuoagent restart
When a broker is running with this balancer installed, you can make that broker passive by executing the JAR file. For example,
java -jar ActivePassive.jar
host with the fully qualified domain name of a host or the IP address of a host. The broker on this host will be made passive or active.
port with the port e specified host is using for remote JMX management. The default is
The last argument is optional.
--activeto make a broker active.
--passiveto make a broker passive.
--statusto determine if a broker is active or passive.
If you omit this argument, the plugin changes an active broker to a passive broker, or changes a passive broker to an active broker.