Implement Strict Routing Semantics for Routing Rules by Peiyingy · Pull Request #804 · trinodb/trino-gateway

Peiyingy · 2025-12-04T03:35:37Z

Description

This PR adds strictRouting flag for routing as proposed in #797.
Routing rules can now support strictRouting: True to force pinning the query to the routing group

When strictRouting = false (default), the routing behavior remains unchanged.
When strictRouting = true, the gateway would not fall back to default clusters if the pinned backend becomes unavailable. Instead, the query should fail immediately with a 404 error.

Testing

mvn clean install
Added new test cases in TestStochasticRoutingManager
Local test to verify the strictRouting flag works

trino> select 1;
Error starting query at http://localhost:8080/v1/statement returned an invalid response: JsonResponse{statusCode=404, headers={content-length=[96], content-type=[text/plain], date=[Thu, 04 Dec 2025 03:45:04 GMT], vary=[Accept-Encoding]}, hasValue=false} [Error: No healthy backends available for routing group 'adhoc1' under strict routing for user 'pye']

clean up code wip add tests

RoeyoOgen · 2025-12-04T12:37:23Z

Just a few remarks:

why "enforceIsolation" and not strictRouting? or noFallback?
does this differ if the routing group is a single cluster rather than a group? - does this clash with your other PR #796?

xkrogen · 2025-12-04T16:21:56Z

why "enforceIsolation" and not strictRouting? or noFallback?

+1 strictRouting is a good name

Peiyingy · 2025-12-04T16:57:46Z

Just a few remarks:

why "enforceIsolation" and not strictRouting? or noFallback?

does this differ if the routing group is a single cluster rather than a group? - does this clash with your other PR #796?

Thanks for the suggesting. I'll change the name to strictRouting
This would also support routing cluster rules. After either of the PR is merged, we just need to rebase the other PR to make sure both strictRouting and cluster routing are supported.

kbhatianr · 2025-12-04T22:11:07Z

gateway-ha/src/main/java/io/trino/gateway/ha/router/BaseRoutingManager.java

        List<ProxyBackendConfiguration> backends = gatewayBackendManager.getActiveBackends(routingGroup).stream()
                .filter(backEnd -> isBackendHealthy(backEnd.getName()))
                .toList();
+        if (backends.isEmpty() && strictRouting) {


This may be a nitpick, but evaluating strictRouting first can short circuit the backends.isEmpty() one, in case it's false. A teeny performance optimization would be to re-order these so it's if (strictRouting && backends.isEmpty())

RoeyoOgen · 2025-12-07T07:28:36Z

gateway-ha/src/main/java/io/trino/gateway/ha/router/BaseRoutingManager.java

                .filter(backEnd -> isBackendHealthy(backEnd.getName()))
                .toList();
+        if (strictRouting && backends.isEmpty()) {
+            throw new WebApplicationException(


why WebApplicationException and not IllegalStateException like in IllegalStateException("Number of active backends found zero"))

or maybe a custom Explicit Exception inherited from RouterException?

felicity3786

Let's also update the official doc?

felicity3786 · 2025-12-08T23:13:08Z

gateway-ha/src/main/java/io/trino/gateway/ha/router/BaseRoutingManager.java

                .filter(backEnd -> isBackendHealthy(backEnd.getName()))
                .toList();
+        if (strictRouting && backends.isEmpty()) {
+            throw new WebApplicationException(


We can add a WARN or ERROR with context when the 404 is triggered? Also +1 on maybe making it a NoBackendAvailableException?

oneonestar

It's ambiguous what you mean strictRouting.

There are two fallback logics in routing.

If RoutingGroupSelector failed to select a routing group for a query, fallback to defaultRoutingGroup.

trino-gateway/gateway-ha/src/main/java/io/trino/gateway/ha/handler/RoutingTargetHandler.java

Lines 97 to 99 in eb736ee

    
           String routingGroup = !isNullOrEmpty(routingDestination.routingGroup()) 
        
                   ? routingDestination.routingGroup() 
        
                   : defaultRoutingGroup;

If there are no available active healthy cluster for the selected routing group, fallback to ActiveDefaultBackends (ie. active healthy cluster in defaultRoutingGroup).

trino-gateway/gateway-ha/src/main/java/io/trino/gateway/ha/router/BaseRoutingManager.java

Line 121 in a4159fc

return selectBackend(backends, user).orElseGet(() -> provideDefaultBackendConfiguration(user));

It's not clear which fallback logic (or both) are disabled. If you decided to disable both (currently you only handled 2), please make sure the error messages are clearly distinguishable for these cases. Docs are also required to explain the exact affect of this config.

oneonestar · 2025-12-10T12:57:07Z

gateway-ha/src/main/java/io/trino/gateway/ha/router/BaseRoutingManager.java

                .toList();
+        if (strictRouting && backends.isEmpty()) {
+            throw new WebApplicationException(
+                             Response.status(NOT_FOUND)


Client did nothing wrong and shouldn't receive a 4xx error. We should return a 5XX indicate a server side error, maybe 503 Service Unavailable.

github-actions · 2026-01-27T17:07:32Z

This pull request has gone a while without any activity. Ask for help on #trino-gateway-dev on Trino slack.

flag wip

d7fe5fc

clean up code wip add tests

cla-bot bot added the cla-signed label Dec 4, 2025

Peiyingy marked this pull request as ready for review December 4, 2025 03:57

rename to strictRouting

2810a25

Peiyingy changed the title ~~Implement Stronger Isolation Semantics for Routing Rules~~ Implement Strict Routing Semantics for Routing Rules Dec 4, 2025

update error msg

ac28ac5

kbhatianr reviewed Dec 4, 2025

View reviewed changes

Peiyingy added 3 commits December 4, 2025 17:17

address comment

54d3c37

small fixes

a4159fc

small fixes

eb736ee

RoeyoOgen reviewed Dec 7, 2025

View reviewed changes

felicity3786 reviewed Dec 8, 2025

View reviewed changes

oneonestar reviewed Dec 10, 2025

View reviewed changes

xkrogen mentioned this pull request Dec 15, 2025

[Darft WIP]Add Best-Effort Routing Fallback When All Backends in Default Group Are Unhealthy #810

Draft

github-actions bot added the stale label Jan 27, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement Strict Routing Semantics for Routing Rules#804

Implement Strict Routing Semantics for Routing Rules#804
Peiyingy wants to merge 6 commits intotrinodb:mainfrom
Peiyingy:Peiyingy/enforceIsolation

Peiyingy commented Dec 4, 2025 •

edited

Loading

Uh oh!

RoeyoOgen commented Dec 4, 2025

Uh oh!

xkrogen commented Dec 4, 2025 •

edited

Loading

Uh oh!

Peiyingy commented Dec 4, 2025

Uh oh!

kbhatianr Dec 4, 2025

Uh oh!

RoeyoOgen Dec 7, 2025

Uh oh!

felicity3786 left a comment

Uh oh!

felicity3786 Dec 8, 2025

Uh oh!

oneonestar left a comment •

edited

Loading

Uh oh!

oneonestar Dec 10, 2025

Uh oh!

github-actions bot commented Jan 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

6 participants

	String routingGroup = !isNullOrEmpty(routingDestination.routingGroup())
	? routingDestination.routingGroup()
	: defaultRoutingGroup;

Conversation

Peiyingy commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Testing

Uh oh!

RoeyoOgen commented Dec 4, 2025

Uh oh!

xkrogen commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Peiyingy commented Dec 4, 2025

Uh oh!

kbhatianr Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

RoeyoOgen Dec 7, 2025

Choose a reason for hiding this comment

Uh oh!

felicity3786 left a comment

Choose a reason for hiding this comment

Uh oh!

felicity3786 Dec 8, 2025

Choose a reason for hiding this comment

Uh oh!

oneonestar left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

oneonestar Dec 10, 2025

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

6 participants

Peiyingy commented Dec 4, 2025 •

edited

Loading

xkrogen commented Dec 4, 2025 •

edited

Loading

oneonestar left a comment •

edited

Loading