Spring boot admin clustering with hazelcast

[soelvar]

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.*

[cdprete]

Are there any news on this?

I actually kind of observed the same even locally without the clustering.

1. If I've an app registered to the server
2. which then I kill by stopping it in the IDE
3. and then I start it again
4. I end up in the UI with 2 instances of the app, one down and one up

[Subrhamanya]

+1 I am also facing the same issue

[cdprete]

From my side, with the application currently deployed (SBA 3.5.0), I'm not facing this issue. But, I've also to say that I'm using Eureka as service registry and not the SBA client self-registration and I'm not in AWS but OCP instead.