Start / Log Check / Shutdown / Initialization

This is how to start, check logs, stop, and initialize the SysMaster DB in a Kubernetes environment.

1. Start

Execute the following commands in the directory where the installation file is located to create Kubernetes objects.

1.1. Create Namespace, ConfigMap, PVC, and Service

kubectl apply -f kubernetes/init

1.2. Create RepoDB and MetaDB deployments (proceed after database creation is complete)

kubectl apply -f kubernetes/db

Before proceeding to the next step, ensure that RepoDB and MetaDB have booted successfully. This can be verified through the following logs.

First, verify that the following messages are displayed in the terminal output logs of each pod.

[ENTRYPOINT LOG]: INFO: Attempting to start PostgreSQL server...

Next, verify that the following message is output in the log file of each database.

LOG: database system is ready to accept connections

The method for checking each database's log file is described in "2. Log check".

1.3. Creating a Kafka deployment (proceed with Kafka pods in the running state)

kubectl apply -f kubernetes/kafka

1.4. Create SysMaster deployment

kubectl apply -f kubernetes/sysmaster

After booting is complete, login and program use are possible. Boot completion can be confirmed via the SDM log with the following log:

Started SdmApplication in ... seconds (JVM running for ...)

---

2. Log check

By default, the users can access the log files of each module by connecting to the containers within the pods. The SysMaster DB modules log files are stored in the following paths within each container.

/sysmaster/logs

Additionally, for user convenience, the users can create and use a dedicated container for log verification.

The sysmasterdb8-log-container, a dedicated log viewing container, is defined within the sysmasterdb8-client-pod specified in the client-deployment.yaml file included in the deployment file configuration. Users can view logs from all SysMaster DB modules by accessing the log directory path (/sysmaster/logs) within this container.

---

3. Shutdown

To terminate SysMaster DB, execute the following commands in the directory where the installation files are located. Note that even after terminating SysMaster DB, the data files in the Repository DB and Meta DB are retained, so the users can use the previously saved data by restarting SysMaster DB.

1.1. Delete the SysMaster deployment

kubectl delete -f kubernetes/sysmaster

1.2. Delete Kafka deployment

kubectl delete -f kubernetes/kafka

1.3. Delete RepoDB and MetaDB deployments

kubectl delete -f kubernetes/db

Note

1. Always delete the SysMaster deployment and Kafka deployment together.

2. RepoDB and MetaDB deployments do not necessarily need to be deleted, and the users can still access RepoDB and MetaDB to check data even after SysMaster is terminated.

---

4. Initialization

Running the following commands will delete all data and restore the system to its initial installation state. However, previously saved data will not be available.

kubectl delete -f kubernetes/init