apache / apache/accumulo

Determine if intermediate caching of property derived configurations can be simplified or removed.

Open
#2,634 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
1.2k
Forks
487
Avg merge
4d 5h
Merged PRs (30d)
13

Description

As a follow-on to single node property storage in ZooKeeper (issue https://github.com/apache/accumulo/issues/1454)

The code contains multiple levels of caching configuration derived from properties. When the single node storage is implemented, the intermediate caching may no longer be necessary and code simplification / clean-up may be possible.

Possible candidate:

- The configuration caching in ServerConfigurationFactory.
- The handling and usage of updateCount in classes that extend AccumuloConfiguration.

Contributor guide

Open the contributing guide

Research direction

Start with issue #1454 to understand the single-node property storage change, then inspect configuration caching in ServerConfigurationFactory and updateCount handling in AccumuloConfiguration subclasses. Determine whether the intermediate caches remain necessary and document the scope of any simplification or cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.