-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway refuses to route to non-adhoc group if adhoc group is unhealthy #587
Comments
What version are you using? |
It was v13 |
What's the ClusterStatsMonitor you are using? Right now we have
|
Also may I know your routing rule's condition? Is it something like |
Sure, apologies - I should have realised that you might need that info! We're using the JDBC monitorType. routing rules is a set like this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
trino-gateway v13. I created these clusters:
Then I added routingrules to send queries to cluster3. I can confirm this by running
select * from system.runtime.nodes
(always returns cluster3).I then set cluster 1 inactive. Everything is fine. I then stop cluster2 and now the queries fail despite the fact that they should be routed to cluster3. This was unexpected. I'm not using analyzeRequest.
config snippet showing active modules:
stacktrace:
The text was updated successfully, but these errors were encountered: