spring-projects / spring-projects/spring-data-redis
Introduce configuration options for `ClusterCommandExecutor` via Jedis
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
see https://github.com/spring-projects/spring-data-redis/blob/125342f19a755e566e0b6b2f218d30cb0b235d43/src/main/java/org/springframework/data/redis/connection/ClusterCommandExecutor.java#L90
why use coreSize 1 by default? when exec unlink keys, will use the executor, it's single thread, so so so slowly!!
Contributor guide
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
Start with src/main/java/org/springframework/data/redis/connection/ClusterCommandExecutor.java around line 90 and inspect how the executor is created and used for commands such as unlink. Determine where configuration can be exposed and verify that the executor's core size is configurable rather than fixed at one; the issue is done when callers can control this setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100