Introduction

There can be situations when a Controller Cluster should be reverted for use with to act as a Standalone Controller:

• In case of an architecture decision to continue with a Standalone Controller.
• In case of severe loss of cluster-related journal data, for example if journals of one of the Controller instances and of the Cluster Watch Agent have not been consistently written to disk or are not available after a server crash or file system crash.

Converting Reverting a Controller Cluster to a Standalone Controller offers to re-instate the Cluster at a any later point in time, see JS7 - How to convert a Standalone Controller to a Controller Cluster.

...

Reverting the Controller Cluster

Stopping the Controller Cluster

As a pre-requisite 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.

• In most situations this will be the previously active Controller instance.
• Users should remove the journal of the previously standby Controller instance , precisely that is no longer in use. More precisely users should remove the contents of the unused Controller instance's state folder. This measure prevents a situation when later on the previous standby unused Controller instance is will be started by chance and invites will invite the Standalone Controller instance to re-establish the cluster.

Reverting the journal of the Controller journal can be instance that should be used as a Standalone Controller is performed with the following command:

# reverting Controller Journaljournal for Unix with no running Controller instances
./controller_instance.sh revoke

# reverting Controller Journal for Unix with a running Controller instance that is stopped and reverted
./controller_instance.sh stop --revokerevert

@rem reverting Controller Journaljournal for UnixWindows with no running Controller instances
./controller_instance.cmd revoke

@rem reverting Controller Journal for Unix with a running Controller instance that is stopped and reverted
.\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 instanceController.
• Standalone Controllers
  • do not connect to a Cluster Watch Agent,
  • do not connect nor can be connected to/from a second Controller instance acting for in a standby role.

Configuring the Standalone Controller

The Controller's administrative menu is invoked from the JOC Cockpit user interface as follows:

From the list of Controllers displayed users select the "Edit" action menu item for the respective Controller:

...

When editing the Controller configuration one of the following popup windows is displayed.

Using JOC Cockpit as Cluster Watch

If JOC Cockpit is assigned the Cluster Watch role then the popup window is offered:

Image Removed

looks like this:

Image Added

JOC Cockpit can be assigned the Cluster Watch role starting from this release:

Using an Agent as Cluster Watch

If an Agent is assigned the Cluster Watch role then the popup window looks like this:

Image Added

Reverting the Cluster

The Standalone and Cluster radio buttons The initial radio buttons Standalone and Cluster determine the Controller type. Users can modify the Controller type to Standalone and enter the URL of the Controller instance that is should be used as a Standalone Controller like this:

When At the point in time when submitting the changes the Controller will not be started. Therefore the Test Connection function button cannot be used.

Starting the Standalone Controller

With the Controller type being reverted modified to Standalone, users can start the Standalone Controller instance from the command line like this:

...

@rem starting the Standalone Controller for Windows from the command line
.\controller_instance.cmd start

@rem starting the Standalone Controller Windows Service from the command line
.\controller_instance.cmd start-service

@rem alternatively the Standalone Controller can be started from the Windows Service Panel

Further Resources

• JS7 - Controller Configuration Items
• JS7 - Controller - Command Line Operation
• JS7 - Agent Command Line Operation
• JS7 - How to convert a Standalone Controller to a Controller Cluster