Spring boot admin clustering with hazelcast
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java, spring-boot
- Domain
- backend, distributed-systems
Research direction
Review the supplied Hazelcast clustering and map configuration alongside Spring Boot Admin's self-registration behavior; no source file, test, or entry point is named. Reproduce the deployment of a new application version in the clustered setup and determine why the old instance remains. Done means obsolete instances are removed from Spring Admin after an application replacement.
Written by the indexing model from the issue text.
Description
Spring Boot Admin Server information
-
Version:
3.1.4 -
Spring Boot version:
3.0.9 -
Configured Security:
N/A -
Webflux or Servlet application:
servlet
Client information
-
Spring Boot versions:
3.0.9 -
Used discovery mechanism:
self registration -
Webflux or Servlet application:
servlet
Description
The clustering is working fine and applications are being clustered on all servers. The problem is that if a new version of a given application is deployed, then the old instance is never removed from Spring Admin.
yaml
hazelcast:
cluster-name: spring-admin
metrics:
enabled: false
management-center:
enabled: false
retention-seconds: 30
jmx:
enabled: false
map:
spring-boot-admin-event-store:
backup-count: 1
in-memory-format: OBJECT
merge-policy:
batch-size: 100
class-name: PutIfAbsentMergePolicy
time-to-live-seconds: 30
eviction:
eviction-policy: NONE
spring-boot-admin-sent-notifications:
backup-count: 1
in-memory-format: OBJECT
merge-policy:
batch-size: 100
class-name: PutIfAbsentMergePolicy
time-to-live-seconds: 30
eviction:
eviction-policy: LRU
network:
reuse-address: true
outbound-ports:
- 33000-35000
port:
auto-increment: false
port: 5701
join:
auto-detection:
enabled: false
multicast:
enabled: false
tcp-ip:
enabled: false
aws:
enabled: true
hz-port: 5701
service-name: dev-admin-server
interfaces:
enabled: true
interfaces:
- 10.171.0-240.*
- Dominant language
- Java
- Stars
- 12.9k
- Forks
- 3.2k
- Avg merge
- 23h 31m
- Merged PRs (30d)
- 72
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from codecentric/spring-boot-admin
-
Bug: Dependency Trees overflows the call stack on cyclic SBOM dependency graphsPossibly taken @faystmax claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
codecentric/spring-boot-admin#5746 ·
Maintainers usually reply within 1 day
-
Bug: Dependency Trees uses dependencies[0] as root instead of metadata.component.bom-refPossibly taken @faystmax claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
codecentric/spring-boot-admin#5745 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
codecentric/spring-boot-admin#5743 ·
Maintainers usually reply within 1 day
-
Bug: Filtering rules are not synchronized between SBA nodesPossibly taken @SteKoe claimed this 4 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
codecentric/spring-boot-admin#5721 · 3 comments ·
Maintainers usually reply within 1 day
-
Bug: Multiple notifications from multiple instancesPossibly taken @YadavKshitiz claimed this 6 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
codecentric/spring-boot-admin#5716 · 1 comment ·
Maintainers usually reply within 1 day
All issues in codecentric/spring-boot-admin
Similar issues
-
[destination-snowflake] Custom domains rejected unlike source connectionsPossibly taken @kuza55 claimed this today. Openautoteam community connectors/destination/snowflake team/use
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
component/operate kind/feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Forge coverage prompts carry text the agent cannot act onPossibly taken @graalvmbot claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
oracle/graalvm-reachability-metadata#10572 ·
Maintainers usually reply within 1 day
-
[CI] Core CI doesn't run for changes to amoro-format-lance (and amoro-web)Possibly taken @MarkAlex1234 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 2 days