Returning Data Cataloging to a running state

Provides detailed instructions to put Data Cataloging in running state on an OpenShift® environment.

About this task

Follow the steps in a specific sequence to put Data Cataloging in to a running state from idle.

Procedure

Start Db2 instance. For procedure, see Stopping and starting a Db2 instance.

It is needed to come back to a running state and ensure that you make replicas back to the previous state in the following order.

Note: It is important to scale up smoothly for those deployments that have two or more replicas and wait for them to be at the ready stage to scale up the next two replicas.

DB2WHRest

Run the following command to get the list of the deployments and filter by db2whrest.

$oc get deployments |grep db2whrest

Example output:

$oc get deployments |grep db2whrest
isd-db2whrest                    0/0     0            0           6d20h

Run the following to command to scale up replicas to 1 for every db2whrest deployment.

$oc scale --replicas=1 deployment <deployment_name>

Example output:

$oc scale --replicas=1 deployment db2whrest
deployment.apps/ db2whrest scaled

Ensure that you have scale up replicas to 1 for every db2whrest deployment.

Example output:

$oc get deployments |grep db2whrest
isd-db2whrest                    1/1     1            1           6d20h

Connection manager

Run the following command to get the list of the deployments and filter by connection manager.

$oc get deployments |grep connmgr

Example output:

$oc get deployments |grep connmgr
isd-connmgr                    0/0     0            0           6d20h

Run the following to command to scale down replicas to 1 for every connection manager deployment.

$oc scale --replicas=1 deployment <deployment_name>

Example output:

$oc scale --replicas=1 deployment connmgr
deployment.apps/ connmgr scaled

Ensure that you have scale up replicas to 1 for every connection manager deployment.

Example output:

$oc get deployments |grep connmgr
isd-connmgr                    1/1     1            1           6d20h

Producers

Run the following command to get the list of the deployments and filter by producer.

$oc get deployments |grep producer

Example output:

isd-producer-ceph-le                    0/0     0            0           6d20h
isd-producer-cos-le                     0/0     0            0           6d20h
isd-producer-cos-scan                   0/0     0            0           6d20h
isd-producer-file-scan                  0/0     0            0           6d20h
isd-producer-protect-scan               0/0     0            0           6d20h
isd-producer-scale-le                   0/0     0            0           6d20h
isd-producer-scale-scan                 0/0     0            0           6d20h

Run the following to command to scale up replicas to 1 for every producer deployment.

$oc scale --replicas=1 deployment <deployment_name>

Example output:

$oc scale --replicas=1 deployment isd-producer-file-scan
deployment.apps/ isd-producer-file-scan scaled

Tip: It is recommended to scale up replicas for two producers and continue with the next two only when they are ready, up-to-date, and available. The object of this is to give OpenShift time to handle these requests properly.
Ensure that you have scale up replicas to 1 for every producer deployment.
Example output:
```
$oc get deployments|grep producer-cos-scan
isd-producer-cos-scan                   1/1     1            1           6d20h
```

Consumers

Run the following command to get the list of the deployments and filter by consumer.

$oc get deployments |grep consumer

Example output:

isd-consumer-ceph-le                    0/0     0            0           2d
isd-consumer-cos-le                     0/0     0            0           2d
isd-consumer-cos-scan                   0/0     0            0           2d
isd-consumer-file-scan                  0/0     0            0           2d
isd-consumer-protect-scan               0/0     0            0           2d
isd-consumer-scale-le                   0/0     0            0           2d
isd-consumer-scale-scan                 0/0     0            0           2d

Run the following to command to scale up replicas to 2 for every consumer deployment.

$oc scale –replicas=2 deployment isd-consumer-file-scan

Example output:

$oc scale –replicas=2 deployment isd-consumer-file-scan
deployment.apps/isd-consumer-file-scan scaled

Tip: It is recommended to scale up replicas for two producers and continue with the next two only when they are ready, up-to-date, and available. The object of this is to give OpenShift time to handle these requests properly.
Ensure that you have scaled up replicas to 10 for every consumer deployment, but you must scale up two at a time.
Example output:
```
$oc get deployments|grep isd-consumer-file-scan
isd-consumer-file-scan		2/2	2	2	2d
```

Some pods might face issues when scaling up the replicas back to 10 in a row. If that happens, then you need to wait for a few minutes, but if it is back to the Running or Ready (1/1) state for a long time, then you need to check for failing pods and delete them. OpenShift will create them again after you delete them.

Run the following to get the list of pods that are not running.

$oc get pods | grep -v Running

Example output:

isd-consumer-file-scan-6d6bbf8487-2asd3                         0/1	Pending   0               2h
isd-consumer-file-scan-6d6bbf8487-ljkws                           0/1	Pending   0               2h
isd-consumer-file-scan-6d6bbf8487-m96hc                          0/1	Pending   0               2h
isd-consumer-file-scan-6d6bbf8487-w55lr                           0/1	Pending   0               2h
isd-consumer-file-scan-6d6bbf8487-z8hqd                           0/1	Pending   0               2h

Run the following command to delete pods that are not running.

$oc delete pod isd-consumer-file-scan-6d6bbf8487-ljkws

Example output:

$oc delete pod isd-consumer-file-scan-6d6bbf8487-ljkws                           
pod "isd-consumer-file-scan-6d6bbf8487-ljkws" deleted

$ oc get pods isd-consumer-file-scan-6d6bbf8487-ljkws  
NAME                                      READY   STATUS        RESTARTS   AGE
isd-consumer-file-scan-6d6bbf8487-ljkws   1/1     Terminating   0          2h

OpenShift will create them again after you delete them.

For example:

$oc get pods|grep consumer-file-scan
isd-consumer-file-scan-6d6bbf8487-4lx8r                           0/1     Running     0               64s

#Check until having 1/1 Running state

$oc get pods|grep consumer-file-scan
isd-consumer-file-scan-6d6bbf8487-4lx8r                           1/1     Running     0               2m39s