stackabletech / stackabletech/spark-k8s-operator
spark history server has empty security.properties
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Affected Stackable version
all
Affected Apache Spark-on-Kubernetes version
No response
Current and expected behavior
The security.properties file should contain custom JVM DNS caching properties like networkaddress.cache.ttl, but in case of the history server, this file is empty.
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
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.
Research direction
Trace how the security.properties file is produced for the Spark history server and compare it with the corresponding file for other Spark components. Verify that the history server output includes the custom JVM DNS caching properties, including networkaddress.cache.ttl, and add or update the relevant test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100