The routing would fails if you are using ClusterStatsJmxMonitor with trino version 477 onwards.
Workaround
- Do not ugrade to trino 477 if you are using this monitor
- Use any other
ClusterStatsMonitor
Cause:
The ClusterStatsJmxMonitor relies on the MBean trino.metadata:name=DiscoveryNodeManager to collect cluster statistics. In Trino release 477, this MBean was removed. The change is documented in Trino PR 26083.