Page History
...
As a prerequisite both active and standby Controller instances have to be terminated.
...
Reverting the Controller Journal
Users decide which Controller instance should become the Standalone Controller to continue operations.
...
Code Block | ||
---|---|---|
| ||
# revokingreverting Controller journal for Unix with no running Controller instances ./controller_instance.sh revokerevert # revokingreverting Controller journal for Unix with a running Controller instance that is stopped and reverted (available starting from release 2.5.1) ./controller_instance.sh stop --revokerevert |
Code Block | ||
---|---|---|
| ||
@rem revokingreverting Controller journal for Windows with no running Controller instances ./controller_instance.cmd revokerevert @rem revokingreverting Controller journal for Windows with a running Controller instance that is stopped and reverted (available starting from release 2.5.1) .\controller_instance.cmd stop --revokerevert |
Explanation:
- Running the above script will remove any cluster related items from the Controller instance's journal.
- This allows the Controller instance to be started as a Standalone Controller.
- Standalone Controllers
- do not connect to a Cluster Watch Agent,
- do not connect nor can be connected to/from a second Controller instance acting in a standby role.
...
Overview
Content Tools