Config FE

In the storage-and-computing separation mode, FE is mainly responsible for SQL parsing related work and is also responsible for interacting with the metadata management component MS. FE usually only needs to deploy 2 services, and the replicas are set to 2. The simplest deployment mode is as follows:

spec:
  feSpec:
    image: {feImage}
    replicas: 2

replace {felmage} with the image version >=3.0.2, that wants to deploy, and update the configuration to the storage-and-computing separation resources to be deployed.

Configure resources

Configure computing resources for services

Add computing resource configuration for the FE service. DorisDisaggregatedCluster reuses K8s requests and limits to configure the resource usage of each component. The following is to configure the FE service using 4c 4Gi:

spec:
  feSpec:
    requests:
      cpu: 4
      memory: 4Gi
    limits:
      cpu: 4
      memory: 4Gi

The above example shows how to configure the computing resources of the FE service to 4c 4Gi mode. After configuring the resources that FE wants to use, update the configuration information to DorisDisaggregatedCluster resources to be deployed.

Configure service storage resources

The storage-and-computing separation cluster FE service is a stateful service. In the K8s deployment mode, the corresponding disk needs to be mounted to store the storage information that the FE service needs to persist.

The following is an example of using the default StorageClass to provide storage services for FE configuration:

spec:
  feSpec:
    persistentVolume:
      persistentVolumeClaimSpec:
        #storageClassName：{storageClassName}
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 200Gi

The above example shows how to add 200Gi storage to the FE service. {storageClassName} is the name of the StorageClass to be used. If it is not filled in, the default StorageClass of the cluster will be used. After configuring the storage information required by the FE service according to the above mode, update the configuration to Storage and computing separation resources to be deployed.

Customized configuration file

In K8s deployment, you can use ConfigMap to mount customized configuration for the FE service to start the FE service. Assume that the FE service is started with the following configuration:

apiVersion: v1
kind: ConfigMap
metadata:
  name: fe-configmap
  namespace: default
  labels:
    app.kubernetes.io/component: fe
data:
  fe.conf: |
    CUR_DATE=`date +%Y%m%d-%H%M%S`
    # Log dir
    LOG_DIR = ${DORIS_HOME}/log
    # For jdk 17, this JAVA_OPTS will be used as default JVM options
    JAVA_OPTS_FOR_JDK_17="-Djavax.security.auth.useSubjectCredsOnly=false -Xmx8192m -Xms8192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=$LOG_DIR -Xlog:gc*:$LOG_DIR/fe.gc.log.$CUR_DATE:time,uptime:filecount=10,filesize=50M --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens java.base/jdk.internal.ref=ALL-UNNAMED"
    # INFO, WARN, ERROR, FATAL
    sys_log_level = INFO
    # NORMAL, BRIEF, ASYNC
    sys_log_mode = NORMAL
    # Default dirs to put jdbc drivers,default value is ${DORIS_HOME}/jdbc_drivers
    # jdbc_drivers_dir = ${DORIS_HOME}/jdbc_drivers
    http_port = 8030
    rpc_port = 9020
    query_port = 9030
    edit_log_port = 9010
    enable_fqdn_mode=true

In K8s deployment, enable_fqdn_mode=true must be set. FE uses the DorisDisaggregatedCluster resource sample of the above ConfigMap:

spec:
  feSpec:
    replicas: 2
    configMaps:
      - name: fe-configmap

In the DorisDisaggregatedCluster resource, the configMaps for mounting ConfigMap is an array. The name of each element represents the ConfigMap name of the current namespace.

Configure the ConfigMap information required by the FE service according to the above mode, and update the configuration to Storage and computing separation resources to be deployed.

Tip

• In K8s deployment, when using ConfigMap to mount customized configuration files, there is no need to add meta_service_endpoint、deploy_mode 以及 cluster_id configurations, and Doris-Operator related services will be added automatically.
• In K8s deployment, when using ConfigMap to mount customized configuration files, must to add enable_fqdn_mode=true.