About Specifying the .spec.ttspec.deleteDbOnNotReadyNode Datum

You can specify the .spec.ttspec.deleteDbOnNotReadyNode datum for both replicated and non-replicated configurations.

Note:

Specifying the .spec.ttspec.deleteDbOnNotReadyNode datum could result in the TimesTen Operator deleting PVCs. Deleting PVCs discards the on-disk copy of TimesTen databases. Use caution when specifying the .spec.ttspec.deleteDbOnNotReadyNode datum.
In a replicated environment, depending on your replication setting, deleting PVCs may not cause data loss. For example, assume the following:

  • The sample-0 database is active and the sample-1 database is standby.

  • The Node on which the sample-0 database is running fails.

  • The TimesTen Operator performs the steps to fail over to sample-1, making it the new active.

  • Even if the Node on which sample-0 was running comes back up, the TimesTen Operator duplicates the database on sample-1 back to sample-0. In this case, the contents of the PVCs for sample-0 are not relevant.

Similarly, if sample-0 is the standby, when sample-0 comes back up, the TimesTen Operator duplicates the database from sample-1. In this case, the database in the PVC on the failed node is not relevant.

In a non-replicated environment, there may be data loss. For example, there may be data in a database that is not in any other replica database. In this case, if the TimesTen Operator deletes PVCs associated with the database, there could be data loss.

In non-replicated environments where TimesTen is used as a read-only cache, specifying the .spec.ttspec.deleteDbOnNotReadyNode datum may be beneficial. If specified, the TimesTen Operator can re-provision the number of replicas, even if one Node fails.