stackabletech / stackabletech/hdfs-operator

Investigate logging configuration and logging tests

Open
#620 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/bug
Dominant language
Rust
Stars
53
Forks
9
Avg merge
1d 13h
Merged PRs (30d)
10

Description

@Jimvin discovered problems with configuring logging.

Configuring logging on role level did not work, role group level worked with the following config:

  journalNodes:
    roleGroups:
      default:
        replicas: 3
        config:
          logging:
            enableVectorAgent: true
            containers:
              journalnode:
                loggers:
                  ROOT:
                    level: DEBUG
                console:
                  level: DEBUG
    configOverrides: *configOverrides

In the logging tests we use the hdfs container https://github.com/stackabletech/hdfs-operator/blob/526f58925ca0ea0f543819f05516d3b70e1e28f3/tests/templates/kuttl/logging/04-install-hdfs-automatic-log.yaml.j2#L31.

Looking at the code, it seems to be hdfs as well:

Not sure how that can work, this needs investigation.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the logging test template at tests/templates/kuttl/logging/04-install-hdfs-automatic-log.yaml.j2 and the referenced Rust definitions in rust/crd/src/lib.rs and rust/operator-binary/src/product_logging.rs. Compare role-level and role-group logging configuration, then run the logging tests to determine why the hdfs container configuration appears to work and what needs changing.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, rust
Domain
observability, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.