Restarting the Data Fabric Cluster

This procedure resumes the startup process for Data Fabric clusters that implement HPE Ezmeral Data Fabric on Kubernetes. This procedure does not apply to bare-metal HPE Ezmeral Data Fabric clusters. This procedure does not restart the entire HPE Ezmeral Runtime Enterprise.

Prerequisites

  • The Data Fabric cluster has been shut down with the edf shutdown cluster command.

  • You must have access to the admin CLI pod (default name: admincli-0)

About this task

Use this procedure to resume startup operations on a Kubernetes Data Fabric cluster that has been shut down with the edf shutdown cluster command or has had its startup process paused by the edf startup pause command.

Procedure

  1. On the Kubernetes master node, access the admin CLI pod.
    For example:
    kubectl exec -it admincli-0 -n <namespace> -- /bin/bash
  2. Execute the edf startup resume command.
    For example:
    edf startup resume

    The startup process for Data Fabric cluster pods, such as CLDB and MFS, resumes.

  3. Verify that the pods are ready.

    You must verify that all Data Fabric services are functional before restarting any Data Fabric operations, such as mirroring, or any tenant applications, such as Spark.

    You can check the status by executing the edf report ready command. Consider the following:
    • This command can take a couple of minutes to execute. You might also notice a delay between the display of the second and the third lines of the output.
    • When you execute this command for the first time, you might see the message that the pods are not ready. You must wait until the Data Fabric is online, to see the message that the pods are ready. It usually takes a few minutes for the Data Fabric to be online, however, it can take up to 30 minutes.

    The following example shows the output when the pods are not ready:

    edf report ready
2021/06/14 23:22:34 [edf reports]: [INFO] Checking if pods are stabilized for upgrade. This may take a minute or two.
2021/06/14 23:22:35 [edf reports]: [INFO] Valid MapR user ticket found, skipping ticket generation
2021/06/14 23:24:31 [edf reports]: [ERROR] Pods are not ready for upgrade
2021/06/14 23:24:31 [edf reports]: [ERROR] Check out /tmp/report-20210614232234 for details

    The following example shows the output when the pods are ready:

    edf report ready
2021/06/14 23:28:01 [edf reports]: [INFO] Checking if pods are stabilized for upgrade. This may take a minute or two.
2021/06/14 23:28:02 [edf reports]: [INFO] Valid MapR user ticket found, skipping ticket generation
2021/06/14 23:29:52 [edf reports]: [INFO] Pods are ready
  4. You can now restart tenant applications and perform other Data Fabric operations.