Guance Base

1 What to do if an issue occurs during the first installation and you need to clean up and reinstall!¶

Note: This only applies to scenarios where an issue occurs during the first installation and a complete removal and reinstallation is required. Please confirm carefully before proceeding with the following cleanup steps!

If an installation issue occurs and you need to completely remove everything and reinstall, you must clean up the following three areas in order to reinstall Guance from Launcher:

1.1 Clean up the installed Guance application services¶

Clean up various Guance application services installed in Kubernetes. On your operations machine, enter the Launcher container and execute the cleanup script that comes with Launcher:

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

sh /config/tools/k8s-clear.sh

1.2 Clean up automatically created databases in MySQL¶

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

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

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 Oceanbase Database¶

Whether it's a PaaS service from a cloud provider or a self-built Oceanbase, you can configure it into launcher as follows. Enter the below information during the initial deployment.

# Example of self-built 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’s for a self-built service via obproxy proxy, so we provide the svc name of obproxy here. You can also bypass obproxy and directly use the svc name of obcluster. Whether to use obproxy can be controlled by configuration files during the deployment phase; if it's a PaaS capability provided by the customer, simply fill in the PaaS address.

# The admin account format is: user@tenant#cluster_name 
user: username
tenant: tenant name
cluster_name: cluster name (optional)

# This parameter is a global parameter. If the customer provides a multi-tenant shared PaaS OceanBase, ensure that adjusting this parameter does not affect other tenants.
ALTER SYSTEM SET open_cursors = 200;