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

Selective Hazelcast support

Open
  • Is something wrong?
#4,773 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@shivanshmishra54 is already working on this.

Since Oct 1, 2026.

  • #5739 by @shivanshmishra54 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, spring-boot
Domain
distributed-systems

Research direction

Start with the server clustering documentation and the behavior described in issues #4258 and #4599. Determine how notification and event caches are configured, then make cache creation independently selectable so notifications can be clustered without events; done means the requested selective configuration works without the reported crashes or duplicate notifications.

Written by the indexing model from the issue text.

Description

type: documentation type: enhancement

Hello.

Enhancement
To my understanding of the docs at https://docs.spring-boot-admin.com/3.5.5/docs/server/server#clustering and from trials I did in the past, to have Hazelcast clustering support in an SBA server, both the notification and event maps need to be configured, because otherwise it would crash (e.g.: https://github.com/codecentric/spring-boot-admin/issues/4258).
Given the weird behavior in https://github.com/codecentric/spring-boot-admin/issues/4599, which is not fixable if not by destroying the environment completely (on rolling updates / zero-downtime deployments, the event cache gets migrated from one old node to new one which is starting automatically), I would like to have the possibility to have only the notifications clustered - in order to avoid duplicates - and not the events as well.
Of course, to make the feature generic enough and profitable also by others, ideally it should be possible to say for each of the caches if they should be created or not.

Dominant language
Java
Stars
12.9k
Forks
3.2k
Avg merge
23h 31m
Merged PRs (30d)
72

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 codecentric/spring-boot-admin

All issues in codecentric/spring-boot-admin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.