Feature: Endpoint detection strategy should be retried
未关闭
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- java, spring-boot
- 领域
- backend
调研方向
Start by reading QueryIndexEndpointStrategy and ProbeEndpointsStrategy, which are named in the issue, and trace where SBA switches between them. Identify how endpoint detection failures are handled and where retry configuration belongs. Done means configurable retries occur before fallback to probing; add or update tests for that behavior.
由索引模型根据 Issue 内容生成。
描述
Hello.
I'm using the latest 4.1.4 version of SBA and I can observe the following behaviour:
2026-10-10T13:44:03.067+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.QueryIndexEndpointStrategy : Querying actuator-index for instance b8b651c9a040 on 'http://foo:8090/actuator' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.086+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/dump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.086+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/health' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/env' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/trace' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/auditevents' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/mappings' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/info' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/jolokia' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/metrics' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/threaddump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/httptrace' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/conditions' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/logfile' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/configprops' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/integrationgraph' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/startup' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/refresh' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/loggers' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/quartz' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/heapdump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/shutdown' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/httpexchanges' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/beans' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/liquibase' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/flyway' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/caches' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/sessions' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/scheduledtasks' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.093+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/sbom' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.093+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/prometheus' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
Basically, if the QueryIndexEndpointStrategy fails, SBA switches automatically to ProbeEndpointsStrategy and starts to flood with requests.
While the behaviour is understandable, it would be nice to have some configurable retries in place before falling back to the ProbeEndpointsStrategy.
- 主要语言
- Java
- 星标
- 12.9k
- 派生
- 3.2k
- 平均合并
- 23 小时 30 分钟
- 30 天内合并 PR
- 111
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
codecentric/spring-boot-admin 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
codecentric/spring-boot-admin#5743 ·
维护者通常 1 天内回复
-
Bug: Multiple notifications from multiple instances可能已有人在做 @YadavKshitiz 于 20 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 55/100
codecentric/spring-boot-admin#5716 · 1 条评论 ·
维护者通常 1 天内回复
-
Bug: Composite health contributors' details are not shown可能重新可做 @cdprete 于 29 天前认领，目前没有进行中的 PR。 未关闭type: enhancement
难度 3/5 1-2 天 新手友好度 52/100
codecentric/spring-boot-admin#5534 · 3 条评论 ·
维护者通常 1 天内回复
-
Feature: Make browser notifications customizable & navigable可能重新可做 @abhiramaab 于 78 天前认领，目前没有进行中的 PR。 未关闭type: enhancement
难度 3/5 1-2 天 新手友好度 55/100
codecentric/spring-boot-admin#5504 · 5 条评论 ·
维护者通常 1 天内回复
-
type: bug
难度 4/5 3-5 天 新手友好度 35/100
codecentric/spring-boot-admin#5482 · 6 条评论 ·
维护者通常 1 天内回复
查看 codecentric/spring-boot-admin 的全部 Issue
相似的 Issue
-
status: waiting-for-triage
难度 2/5 1-3 小时 新手友好度 79/100
spring-projects/spring-ai#7206 ·
维护者通常 2 天内回复
-
area/cli
难度 2/5 半天 新手友好度 78/100
quarkusio/quarkus#57623 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
jhipster/prettier-java#1113 ·
维护者通常 2 天内回复
-
bug follow-up lane:backlog
难度 2/5 1-3 小时 新手友好度 82/100
Sanne/incus-spawn#1576 · 1 条评论 ·
维护者通常 1 天内回复
-
Pasting code into a comment adds imports for the pasted code可能已有人在做 @ravnskjaer 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 79/100
eclipse-jdt/eclipse.jdt.ui#3275 · 1 条评论 ·
维护者通常 1 天内回复