wlswo commented on PR #19480:
URL: https://github.com/apache/druid/pull/19480#issuecomment-4483797072
Closing in favor of #19481 after verifying this against a live Druid 30
cluster.
`/druid/coordinator/v1/servers?simple` is backed by `InventoryView` and only
reports segment-loading servers —
brokers don't appear in it unless they hold broadcast segments, which is
rare in practice. Confirmed empirically: on
the cluster I tested, the endpoint returned only `historical` and
`indexer-executor` entries even though the cluster
had a running broker on a separate host.
So the broker filter added in this PR would always count zero. The real bug
is broader: the coordinator-only fallback
was using the wrong endpoint, and `overlord`, `coordinator`, `router`,
`broker`, and `indexer` were all silently
dropped — not just broker. The new PR switches the endpoint to
`/druid/coordinator/v1/cluster` (discovery-backed,
same source `sys.servers` uses) and brings the fallback in line with the SQL
branch.
Sorry for the noise.
--
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]
