server_permanent_offline_time

Description

server_permanent_offline_time specifies the threshold for the time interval between the last heartbeat of an OBServer node and the time when the node is considered permanently offline. When an OBServer node is permanently offline, the Root Service handles the data replicas on the node by removing them from the Paxos member group and replicating them to other available OBServer nodes to ensure the integrity of the Paxos member group.

Privilege requirements

• Query the parameter

  The sys tenant and all user tenants can query this parameter by using the SHOW PARAMETERS statement or the GV$OB_PARAMETERS view.

• Modify the parameter

  Only the sys tenant can modify this parameter. User tenants cannot modify this parameter.

Attributes

Considerations

By setting this parameter, you can avoid unnecessary replica replication. The system only starts the replication of data replicas on permanently offline nodes when the replicas are lost for longer than the specified time.

The applicable scenarios and recommended values of this parameter are as follows:

• OceanBase Database version upgrade: We recommend that you set this parameter to 72h.

  Note

  When you use OCP V2.3.5 or later to upgrade OceanBase Database V2.1.2 or later, the system automatically sets this parameter to 72h.

• Hardware replacement of an OBServer node: We recommend that you set this parameter to 4h.

• An OBServer node is cleared and comes online: We recommend that you set this parameter to 10m to enable the cluster to come online quickly.

Examples

Set the threshold for the time interval between the last heartbeat of an OBServer node and the time when the node is considered permanently offline to 3600s.

obclient> ALTER SYSTEM SET server_permanent_offline_time = '3600s';

References

For more information about the Root Service, see Database high availability.