stackabletech / hive-operator

Other
21 stars 1 forks source link

Ability to Override the Hive metastre LOG Configuration #528

Open CoderYellow opened 2 weeks ago

CoderYellow commented 2 weeks ago

below configOverrides is not working for metastore-log4j2.properties

apiVersion: hive.stackable.tech/v1alpha1
kind: HiveCluster
metadata:
  name: hive-postgres-s3
  namespace: "data"
spec:
  image:
    productVersion: 3.1.3
  clusterConfig:
    listenerClass: external-stable
    database:
      connString: jdbc:postgresql://hms-pg-cluster:5432/hive
      credentialsSecret: hive-credentials
      dbType: postgres
    s3:
      reference: oss
  metastore:
    configOverrides:
      metastore-log4j2.properties:
        rootLogger.level: "DEBUG"
      security.properties:
        rootLogger.level: "DEBUG"
    roleGroups:
      default:
        replicas: 1

Image

CoderYellow commented 2 weeks ago

Is there currently a way to customize the log level for the metastore? Can this be configured within the HiveCluster CRD? Without this capability, troubleshooting becomes significantly more challenging.

sbernauer commented 2 weeks ago

Hi @CoderYellow, we don't support configOverrides on all files, so the metastore-log4j2.properties is not supported.

However, what you probably want to do is use the logging mechanism we have added to the platform, which allow you fine-grained control, regardless of the actual different logging implementations in all the different tools. You can find the documentation here: https://docs.stackable.tech/home/stable/concepts/logging, the specific one for Hive metastore here: https://docs.stackable.tech/home/stable/hive/usage-guide/logging

Without having tested it, your config could look something like

spec:
  metastore:
    config:
      logging:
        containers:
          hive:
            console:
              level: DEBUG
            loggers:
              ROOT:
                level: DEBUG
sbernauer commented 3 days ago

Hi @CoderYellow I see you reacted with a heart, am I correct to assume your problem is fixed? :)