Add option to enable and configure trash to the CRD

Open
  • Is something wrong?
#853 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
61/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes, rust
Domain
infrastructure

Research direction

Read the HDFS CRD and the code that maps CRD settings to Hadoop configuration, focusing on fs.trash.interval and the existing configOverrides behavior. Identify how comparable HDFS settings are exposed and configured, then follow the related tests or examples. Done means users can configure the trash interval through the CRD and the configured value reaches HDFS.

Written by the indexing model from the issue text.

Description

The Stackable HDFS operator currently does not set a value for fs.trash.interval causing HDFS to use the default value 0. This means that trash is disabled by default and can be enabled using configOverrides if needed. Since this is a commonly used feature for HDFS it would make sense to make the trash interval configurable in the CRD.

Dominant language
Rust
Stars
53
Forks
10
Avg merge
1d 5h
Merged PRs (30d)
12

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from stackabletech/hdfs-operator

All issues in stackabletech/hdfs-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.