GuanceDB
1 GuanceDB Storage Component Scaling¶
Problem Description: Due to increased metric data ingestion, GuanceDB storage component needs to be scaled out.
Solution:
Scale out the storage component:
# Change the number of replicas based on actual requirements
kubectl -n middleware scale sts guancedb-cluster-guance-storage --replicas=2
Modify the insert and select container configurations:
# Modify insert and select configurations
kubectl -n middleware edit deploy guancedb-cluster-guance-select
kubectl -n middleware edit deploy guancedb-cluster-guance-insert
# Add the new pod to the startup parameters
- --storageNode=guancedb-cluster-guance-storage-1.guancedb-cluster-guance-storage.middleware.svc.cluster.local:8401
- --storageNode=guancedb-cluster-guance-storage-2.guancedb-cluster-guance-storage.middleware.svc.cluster.local:8401
2 Container Deployment Error for GuanceDB¶
Problem Description: When deploying GuanceDB in a container, the service fails to start with the error message: This program can only be run on AMD64 processors with v3 microarchitecture support.
Solution: The CPU architecture of the provided server is not supported. Use a server that supports the v3 microarchitecture.