Scaling Down OIG Instances

11.3 Scaling Down OIG Instances

Scaling down Oracle Identity Governance (OIG) servers is performed in exactly the same way as in Scaling Up OIG Instances except the replicaCount is reduced to the required number of servers.

To stop one or more OIG servers, perform the following steps:

Run the following command to edit the cluster:
- For OIG managed servers:
```
kubectl edit cluster <domainUID>-oim-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster governancedomain-oim-cluster -n oigns
```
- For SOA managed servers:
```
kubectl edit cluster <domainUID>-soa-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster governancedomain-soa-cluster -n oigns
```
Note:
This opens an edit session for the cluster where parameters can be changed using standard vi commands.
In the edit session, search for spec:, and then look for the replicas parameter under clusterName: <cluster>.
In the example below replicas is set to “3”, hence three OIG managed servers are started (oim_server1 - oim_server3):
```
...
spec:
  clusterName: oim_cluster
  replicas: 3
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -Djava.security.egd=file:/dev/./urandom -Xms8192m -Xmx8192m
...
```

To stop OIG servers, decrease the replicas value as desired. In the example below, two managed servers will be stopped by setting replicas to “1”:

...
spec:
  clusterName: oim_cluster
  replicas: 1
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -Djava.security.egd=file:/dev/./urandom -Xms8192m -Xmx8192m
...

Save the file and exit (:wq!).
The output will look similar to the following:
```
cluster.weblogic.oracle/governancedomain-oim-cluster edited
```

Run the following command to view the pods:

kubectl get pods -n <domain_namespace>

For example:

kubectl get pods -n oigns

The output will look similar to the following:

NAME                                                        READY   STATUS      RESTARTS   AGE
governancedomain-adminserver                                1/1     Running       0          23h
governancedomain-oim-server1                                1/1     Running       0          23h
governancedomain-oim-server2                                1/1     Running       0          7m30s
governancedomain-oim-server3                                1/1     Terminating   0          7m30s
governancedomain-soa-server1                                1/1     Running       0          23h

One pod now has a STATUS of Terminating (governancedomain-oim-server3).

The server will take a minute or two to stop. Once terminated the other pod (governancedomain-oim-server2) will move to Terminating and then stop.

The servers will take several minutes to stop so keep executing the command until the pods have disappeared:

NAME                                                        READY   STATUS      RESTARTS   AGE
governancedomain-adminserver                                1/1     Running     0          23h
governancedomain-oim-server1                                1/1     Running     0          23h
governancedomain-soa-server1                                1/1     Running     0          23h