Guance Foundation

1 What Should I Do If Problems Occur During Initial Installation and I Need to Clean and Reinstall?¶

Note: This applies only to scenarios where problems occur during the initial installation and you need to completely remove everything and reinstall. Please carefully confirm before proceeding with the following cleanup steps!

If installation issues occur and you need to completely remove everything and reinstall, you must clean up the following three parts before you can restart the installation from Launcher and reinstall Guance:

1.1 Clean Up Installed Guance Application Services¶

To clean up the various Guance application services already installed in Kubernetes, you can enter the Launcher container on the operations machine and execute the cleanup script that comes with Launcher:

kubectl exec -it launcher-xxxxxxxx-xxx -n launcher /bin/bash

launcher-xxxxxxxx-xxx is the name of your launcher service pod!

After entering the container, you can see the Launcher service's built-in k8s-clear.sh script (/config/tools/k8s-clear.sh). Running this script will clean up all Guance application services and Kubernetes resources:

sh /config/tools/k8s-clear.sh

1.2 Clean Up the Database Automatically Created in MySQL¶

You can enter the Launcher container, which includes a MySQL client tool, and connect to the Guance MySQL instance using the following command:

mysql -h <MySQL instance host> -u root -P <MySQL port> -p  

You need to connect using a MySQL admin account. After connecting, execute the following six MySQL database and user cleanup commands:

drop database df_core;
drop user df_core;
drop database df_func;
drop user df_func;
drop database df_dialtesting;
drop user df_dialtesting;

2 How to Configure Guance to Use an OceanBase Database¶

Whether it is a PaaS service from a cloud provider or a self-hosted OceanBase, you can configure it into Launcher by entering the following information during initial deployment:

# Example for self-hosted setup
MySQL HOST: svc-obproxy.oceanbase.svc.cluster.local
Port: 2883
Admin account: croot@guance
Admin password: root_password
# MySQL HOST: In this example, it is a self-hosted service proxied through obproxy. The value here is the obproxy service name. You can also bypass obproxy and use the obcluster service name directly. Whether to use obproxy can be controlled through the deployment configuration file. If the customer provides a cloud provider PaaS, fill in the PaaS address directly.

# The admin account format is: user@tenant#cluster_name 
user: username
tenant: tenant name
cluster_name: cluster name, can be omitted

When Guance applications use OceanBase, the open_cursors parameter of OceanBase must be set. Execute the following command:

# This parameter is a global parameter. If the customer provides a PaaS OceanBase that is shared by multiple tenants, please confirm whether adjusting this parameter will affect other tenants.
ALTER SYSTEM SET open_cursors = 200;