Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for Redis clustering

Open
  • Is something wrong?
#171 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, redis
Domain
databases, distributed-systems

Research direction

The issue names no files, tests, or entry points; start by reviewing issue #32 and the existing Redis handling in java-cfenv. Resolve which signaling format to support and verify that the chosen approach sets spring.redis.cluster.nodes from a usable cluster node.

Written by the indexing model from the issue text.

Description

enhancement

Similar to #32, I'd like to propose adding support for Redis clustering to java-cfenv. Since Redis clustering allows for node discovery via the various CLUSTER commands, there is greater flexibility in how cluster support can be signaled. One nice aspect is that only a single node need be provided in order for additional nodes to be discovered.

For spring-data-redis to enable clustering, I believe it is only required that the property spring.redis.cluster.nodes be set.

Here are some proposals on how this could be implemented:

  • If the service instance tag also contains the word cluster, (in addition to redis), then the uri is used to determine a host:port to set in spring.redis.cluster.nodes.
  • If the uri scheme is either redis-cluster or rediss-cluster, then the uri is used to determine the host:port of the cluster.
  • An additional array of redis_nodes is provided; for example:
"redis_nodes": [
  {
    "hostname": "x.x.x.x",
    "port": "xxxx"
  },
  {
    "hostname": "x.x.x.x",
    "port": "xxxx"
  }
]

I'd be happy to provide a PR for this work.

Dominant language
Java
Stars
97
Forks
64
Avg merge
6h 36m
Merged PRs (30d)
6

Getting set up

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 pivotal-cf/java-cfenv

All issues in pivotal-cf/java-cfenv

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.