Chapter 4. RHOSO memcached clusters
By default, all the Red Hat OpenStack Services on OpenShift (RHOSO) services in the control plane target a single memcached cluster that contains three memcached servers. This cluster is configured using a single memcached resource created by the memcached service Operator infra-operator, which creates the pods that host the memcached servers and the OpenShift service objects that expose the memcached service.
4.1. Monitoring the startup of the memcached service and its pods Copy linkLink copied to clipboard!
You can use the following command to monitor the memcached startup, which displays the startup state in the MESSAGE column and the service availability in the READY column:
$ oc get memcached
NAME READY MESSAGE
memcached True Setup complete
In this example, because the READY column is True, the memcached service is ready, which means that its associated pods are started and ready to accept traffic.
You can use the following command to determine the status of the memcached pods:
$ oc get pods -l memcached/name=memcached
NAME READY STATUS RESTARTS AGE
memcached-0 1/1 Running 0 2d4h
memcached-1 1/1 Running 0 15m
memcached-2 1/1 Running 0 15m
You can use the following command to describe the type of the memcached service and which ports are open:
$ oc get service memcached
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
memcached ClusterIP None <none> 11211/TCP,11212/TCP 2d4h
The CLUSTER-IP column entry is None because the memcached pods are accessed directly by name through the Red Hat OpenStack Services on OpenShift (RHOSO) components. The memcached service is used only to maintain a list of DNS records for each memcached pod.