Investigate logging configuration and logging tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes, rust
- Domain
- observability, testing-qa
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.
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:
- https://github.com/stackabletech/hdfs-operator/blob/526f58925ca0ea0f543819f05516d3b70e1e28f3/rust/crd/src/lib.rs#L1036
- https://github.com/stackabletech/hdfs-operator/blob/526f58925ca0ea0f543819f05516d3b70e1e28f3/rust/crd/src/lib.rs#L1174
- https://github.com/stackabletech/hdfs-operator/blob/526f58925ca0ea0f543819f05516d3b70e1e28f3/rust/crd/src/lib.rs#L1296
- https://github.com/stackabletech/hdfs-operator/blob/526f58925ca0ea0f543819f05516d3b70e1e28f3/rust/operator-binary/src/product_logging.rs#L156
Not sure how that can work, this needs investigation.
- Dominant language
- Rust
- Stars
- 53
- Forks
- 9
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/hdfs-operator
-
Topology Provider permissions briefly dropped during reconciliation when the reflector watch resets Opentype/bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
stackabletech/hdfs-operator#774 ·
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
stackabletech/hdfs-operator#773 ·
-
type/internal-debt
Difficulty 5/5 Over a week Newbie friendliness 15/100
stackabletech/hdfs-operator#769 ·
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
stackabletech/hdfs-operator#763 ·
-
type/bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
stackabletech/hdfs-operator#712 ·
All issues in stackabletech/hdfs-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100