Scaling Down OAM Servers

12.3 Scaling Down OAM Servers

Scaling down Oracle Access Management (OAM) servers is performed in exactly the same way as in Scaling Up OAM Servers except the replicaCount is reduced to the required number of servers.

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

Run the following command to edit the cluster:
- For OAM managed servers:
```
kubectl edit cluster accessdomain-oam-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster accessdomain-oam-cluster -n oamns
```
- For OAM policy manager servers:
```
kubectl edit cluster accessdomain-policy-cluster -n <domain_namespace>
```
  For example:
```
kubectl edit cluster accessdomain-policy-cluster -n oamns
```
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 OAM managed servers are started (access-domain-oam_server1 - access-domain-oam_server3):
```
...
spec:
  clusterName: oam_cluster
  replicas: 3
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -XX:+UseContainerSupport -Djava.security.egd=file:/dev/./urandom -Xms8192m
        -Xmx8192m
...
```

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

...
spec:
  clusterName: oam_cluster
  replicas: 1
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: -XX:+UseContainerSupport -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/accessdomain-oam-cluster edited
```

Run the following command to view the pods:

kubectl get pods -n <domain_namespace>

For example:

kubectl get pods -n oamns

The output will look similar to the following:

NAME                                                     READY   STATUS        RESTARTS   AGE
accessdomain-adminserver                                 1/1     Running       0          3h45m
accessdomain-oam-policy-mgr1                             1/1     Running       0          3h37m
accessdomain-oam-server1                                 1/1     Running       0          3h37m
accessdomain-oam-server2                                 1/1     Running       0          6m14s
accessdomain-oam-server3                                 1/1     Terminating   0          6m14s

One pod now has a STATUS of Terminating (accessdomain-oam-server3).

The server will take a minute or two to stop. Once terminated the other pod (accessdomain-oam-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
accessdomain-adminserver                                 1/1     Running     0          3h48m
accessdomain-oam-policy-mgr1                             1/1     Running     0          3h40m
accessdomain-oam-server1                                 1/1     Running     0          3h40m