Resume Management

If a TimesTenClassic object is in the ManualInterventionRequired state, you can instruct the TimesTen Operator to examine the state of TimesTen and its databases to see if they are healthy. For the procedures for replicated objects, proceed to About Bringing Up One Database.

For non-replicated objects, set the object's .spec.ttspec.reexamine datum. Doing so instructs the TimesTen Operator to move the object to the Reexamine state. In the Reexamine state, the TimesTen Operator examines the state of TimesTen and its databases. If healthy, the Operator returns the object to the AllReplicasReady state. If not healthy, the object re-enters the ManualInterventionRequired state.

  1. Review the TimesTenClassic objects that are running in your namespace.
    kubectl get ttc

    The output is similar to the following:

    
    NAME             STATE                        ACTIVE           AGE
    samplenorep      ManualInterventionRequired   N/A              2d1h
    ...

    The replicated samplenorep object is in the ManualInterventionRequired state.

  2. Instruct the TimesTen Operator to resume management of the samplenorep object.
    1. Use the kubectl edit command to edit the object.

      If there is a line for .spec.ttspec.reexamine in the file, then modify its value. It must be different than the current value. If there is no line, add a line and specify a value.

      This example adds the .spec.ttspec.reexamine datum and sets the value to reexamineNow.

      kubectl edit ttc samplenorep
      
      # Please edit the object below. Lines beginning with a '#' will be ignored,
      # and an empty file will abort the edit. If an error occurs while saving this file will be
      # reopened with the relevant failures.
      #
      apiVersion: timesten.oracle.com/v4
      kind: TimesTenClassic
      metadata:
      ...
      spec:
        ttspec:
          additionalMemoryRequest: 2Gi
          automaticMemoryRequests: true
          cacheCleanup: true
          createASReadinessProbe: true
          daemonLogCPURequest: 200m
          daemonLogMemoryRequest: 200Mi
          reexamine: rexamineNow
      ...
    2. Save and close the file.
  3. Observe the behavior.
    kubectl get events

    The output is similar to the following. Not all output is displayed.

    27s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-0 state was ManualInterventionRequired, now Reexamine
    27s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-1 state was ManualInterventionRequired, now Reexamine
    27s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-2 state was ManualInterventionRequired, now Reexamine
    27s         Normal    StateChange   timestenclassic/samplenorep      TimesTenClassic was ManualInterventionRequired, now Reexamine
    22s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-0 state was Reexamine, now Normal
    22s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-1 state was Reexamine, now Normal
    22s         Normal    StateChange   timestenclassic/samplenorep      Pod samplenorep-2 state was Reexamine, now Normal
    22s         Normal    StateChange   timestenclassic/samplenorep      TimesTenClassic was Reexamine, now AllReplicasReady
    

    The TimesTen Operator changed the state of each TimesTen Pod from ManualInterventionRequired to Reexamine and changed the TimesTenClassic object's state from ManualInterventionRequired to Reexamine. The TimesTen Operator examined TimesTen and its databases. Since TimesTen and its databases are healthy and functioning properly, the TimesTen Operator changed the state of the TimesTen Pods to Normal and the state of the TimesTenClassic object to AllReplicasReady.