DocumentationGrafana MimirSet upDeploy with Jsonnet and TankaMigrate query-scheduler to ring-based service discovery

Migrate query-scheduler from DNS-based to ring-based service discovery

The query-scheduler supports two service discovery mechanisms:

• DNS-based service discovery
• Ring-based service discovery

To migrate the query-scheduler from DNS-based to ring-based service discovery when your Mimir cluster is deployed using Jsonnet:

1. Configure the query-scheduler instances to join a ring, but keep the querier and query-frontend instances discovering query-schedulers via DNS:
   jsonnet Copy

   {
     _config+:: {
       query_scheduler_service_discovery_mode: 'ring',
       query_scheduler_service_discovery_ring_read_path_enabled: false,
     }
   }

2. Wait until query-scheduler changes have been applied.
3. Open the query-scheduler ring status page and ensure all query-scheduler instances are registered to the ring.
4. Configure query-frontend and querier instances to discover query-schedulers via the ring:
   jsonnet Copy

   {
     _config+:: {
       query_scheduler_service_discovery_mode: 'ring',
       query_scheduler_service_discovery_ring_read_path_enabled: true,
     }
   }