Statuses

The replica states of an API can be inspected by running cortex describe <api-name>. Here are the possible states for each replica in an API:

State

Meaning

Ready

Replica is running and it has passed the readiness checks

ReadyOutOfDate

Replica is running and it has passed the readiness checks (for an out-of-date replica)

NotReady

Replica is running but it's not passing the readiness checks; make sure the server is listening on the designed port of the API

Pending

Replica is in a pending state (waiting to get scheduled onto a node)

Creating

Replica is in the process of having its containers created

ErrImagePull

Replica was not created because one of the specified Docker images was inaccessible at runtime; check that your API's docker images exist and are accessible via your cluster's AWS credentials

Failed

Replica couldn't start due to an error; run cortex logs <name> to view the logs

Killed

Replica has had one of its containers killed

KilledOOM

Replica was terminated due to excessive memory usage; try allocating more memory to the API and re-deploy

Stalled

Replica has been in a pending state for more than 15 minutes; see troubleshooting‚Äč

Terminating

Replica is currently in the process of being terminated

Unknown

Replica is in an unknown state