Site Roles

The following is a list of applicable site roles:

Note
  • The Cachepod/ETCD and the CDL Replication happen during all the roles mentioned in the following section.

  • If the GR links are down or under periodic heartbeat fails, then these GR triggers get suspended.

  • PRIMARY: In this role, the site is in ready state and actively taking traffic for the given instance.

  • STANDBY: In this role, the site is in standby mode, ready to take traffic, but not taking traffic for the given instance.

  • STANDBY_ERROR: In this role, the site is in problem state, not active, and not ready to take traffic for the given instance.

    Note

    When the instance role is in STANDBY_ERROR, data replication gets halted. The command show georeplication-status consistently fails under this condition. However, once the instance role gets transitioned to STANDBY, data replication resumes automatically, and the command displays the result as pass.

  • FAILOVER_INIT: In this role, the site has started to fail over and not in condition to take traffic. The buffer time is two seconds for the application to complete their activity.

For fresh installation, the site boots-up with the following roles:

  • PRIMARY: In this role, the site is in for the local instance (each site has local instance-id configured to identify the local instance). It’s recommended not to configure the pods for monitoring during fresh installation. Once the setup is ready, you can configure the pods for monitoring.

  • STANDBY: In this role, the site is in for other instances.

For upgrades, the site boots-up with the following roles:

  • STANDBY_ERROR: In this role, the site is for all the instances as moving the traffic post upgrade needs manual intervention.