Liveness and Availability Configuration

In order to ensure the high availability of services, K8s automatically restarts the corresponding pod if a component (CN, DN, GMS, CDC) is found to be inactive. However, in certain situations where we need to restart the cn process (due to a parameter modification) or investigate the cause of a process failure, we prefer that K8s does not delete the cn pod due to liveness failure. In such cases, you can use the following command to disable liveness for all CN nodes:

kubectl annotate pod -l polardbx/role=cn runmode=debug

Alternatively, you can disable liveness for a specific cn pod:

kubectl annotate pod {pod name} runmode=debug

To re-enable liveness for a cn:

kubectl annotate --overwrite pod {pod name} runmode-

results matching ""

    No results matching ""