The tungsten_reset_manager command was added in versions 5.3.7 and 6.0.5
The tungsten_reset_manager assists with the graceful
reset of the
manager's dynamic state files on disk.
The tungsten_reset_manager command stops the manager and then deletes the manager's dynamic state files.
For a proper service-wide reset to work, this command needs to be run on every node within the local cluster to ensure all managers have been stopped at the same time. This prevents any manager from storing an old state in memory.
The dynamic state files are automatically rebuilt when the manager is started.
directory needs to be emptied, for example, given a service name of
alpha and a TUNGSTEN_HOME of
/opt/continuent, the full path would be
The tungsten_reset_manager command requires the cluster to be in MAINTENANCE mode first.
tungsten_reset_managerPolicy is not MAINTENANCE. Please select one node only and execute `echo "set policy maintenance" | cctrl` If you are sure the policy is maintenance you may proceed by using -f or --force
By default, the command expects the manager to be running so the policy
may be checked. If you are sure the policy is maintenance you may
proceed by using ether the
Table 9.66. tungsten_reset_manager Options
Below is a sample session.
First, set policy to maintenance on a single node only:
echo "set policy maintenance" | cctrlTungsten Clustering 6.0.4 build 27 north: session established, encryption=false, authentication=false [LOGICAL] /alpha > set policy maintenance policy mode is now MAINTENANCE [LOGICAL] /alpha > Exiting...
Enable maintenance mode on a single host only.
On all nodes in the local cluster, execute the tungsten_reset_manager command:
tungsten_reset_managerAbout to stop the manager and empty directory: /opt/continuent/tungsten/cluster-home/conf/cluster/north/datasource Do you wish to continue? [y/N] y Stopping Tungsten Manager Service... Stopped Tungsten Manager Service. Manager directory /opt/continuent/tungsten/cluster-home/conf/cluster/north/datasource cleared. Done! Make sure all nodes have been cleared first, then execute `manager start` on each node one-by-one, starting with the Primary. When all managers are running, pick one node and execute `echo "set policy automatic" | cctrl`
Once the tungsten_reset_manager command has completed successfully on all nodes in the local cluster, execute the manager start command on all nodes:
manager startStarting Tungsten Manager Service... Waiting for Tungsten Manager Service.......... running: PID:3562
manager has started successfully on all nodes in
the local cluster, set policy to automatic on a single node only:
echo "set policy automatic" | cctrlTungsten Clustering 6.0.4 build 27 north: session established, encryption=false, authentication=false [LOGICAL] /alpha > set policy automatic policy mode is now AUTOMATIC [LOGICAL] /alpha > Exiting...
Enable automatic mode on a single host only.
At this point, the manager state should be completely back to normal. Check
it using the cctrl>