About Suspending Management

There may be a situation in which you want to manually perform maintenance operations. In such a situation, you do not want the Operator to interfere and attempt to perform repair or recovery operations on your grid and database.

One alternative is to stop the Operator (by deleting the timesten-operator Deployment). This action prevents the Operator from interfering or performing repair/recovery operations. However, if you have more than one TimesTenScaleout object deployed in your Kubernetes environment and you delete the Operator, this interferes with the management of all the TimesTenScaleout objects, when perhaps only one of them needs manual intervention.

Another approach is to ask the Operator to take no action for one TimesTenScaleout object. To do this, specify a TimesTenScaleout object's .spec.ttspec.stopManaging datum. The Operator examines the value of .spec.ttspec.stopManaging and if it has changed since the last time the Operator examined it, the Operator changes the state of the TimesTenScaleout object to ManualInterventionRequired. This causes the Operator to no longer examine the status of the grid and database. Nor does the Operator examine the Pods, the containers, and the instances associated with this particular TimesTenScaleout object. For an example showing how to set the .spec.ttspec.stopManaging datum for a TimesTenScaleout object, see Suspend Management.

To cause the Operator to resume management of the TimesTenScaleout object, change the value of the object's .spec.ttspec.reexamine datum. See Set reexamine Datum for details.

See TimesTenScaleoutSpecSpec for information about the TimesTenScaleout object definition.