Oxidaner opened a new issue, #1578: URL: https://github.com/apache/dubbo-admin/issues/1578
Parent: #1491 Phase 4 (part 1) — a unified-Resource-driven service availability index. ### Scope - `LiveServiceIndex` computed from the unified instance Resources plus discovery synchronization state, producing the three states `ACTIVE`, `INACTIVE`, `UNKNOWN`. - Fill in the common Resource contract in the discovery adapters where it is still incomplete (Nacos, ZooKeeper), so the index can be built without touching registry-native objects. - Grace period for confirmed-down tools. ### Acceptance criteria - `LiveServiceIndex` never reads registry-native objects (no Nacos dataId, no ZooKeeper node path, no raw instance payload) and never participates in provider selection. - A tool whose service is confirmed `INACTIVE` beyond the grace period (default 60s, configurable) disappears from `tools/list`. - `UNKNOWN` — which can be caused by Admin startup or a discovery failure — keeps the tool listed. - Equivalent Nacos and ZooKeeper Resources produce identical availability results. - The MCP packages contain no registry-specific SDK dependency. Any missing health/protocol/interface-level registration normalization is fixed in the discovery adapter/subscriber layer, not in the MCP code. - Liveness is not a publish gate: it only produces a warning. - Interface-level and application-level registration liveness are implemented as two separate paths, and each path is covered by its own test cases. ### PR PR-5 — `LiveServiceIndex` and common Resource contract tests. Dependency: Phase 2 (PR-2). May be developed in parallel with PR-3 once the interface contract is stable. Detailed design: [proposal §15 (line 1243)](https://github.com/Oxidaner/dubbo-admin/blob/213bd38dbcfbe0c5bac64c7c8b949651f1633ca9/docs/proposal/mcp-server-proposal.md?plain=1#L1243) — design PR #1541. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
