Feature: Endpoint detection strategy should be retried
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 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分
- マージ済み PR(30日)
- 111
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
codecentric/spring-boot-admin のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
codecentric/spring-boot-admin#5743 ·
メンテナーはふだん 1 日以内に返信
-
Bug: Multiple notifications from multiple instances対応中かも @YadavKshitiz が 19 日前に担当しました。 オープン
難易度 4/5 3〜5日 初心者へのやさしさ 55/100
codecentric/spring-boot-admin#5716 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Bug: Composite health contributors' details are not shown再び着手できるかも @cdprete が 28 日前に担当しましたが、オープン中のプルリクエストはありません。 オープンtype: enhancement
難易度 3/5 1〜2日 初心者へのやさしさ 52/100
codecentric/spring-boot-admin#5534 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
Feature: Make browser notifications customizable & navigable再び着手できるかも @abhiramaab が 77 日前に担当しましたが、オープン中のプルリクエストはありません。 オープン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
-
難易度 2/5 1〜3時間 初心者へのやさしさ 61/100
Vakore/ZappierGames#162 ·
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
[Bug] Lock owned by another client (e.g. Text app) cannot be unlocked from the app対応中かも @falkloewert が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
bug grammar sev-0
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100