Skip to content

Do not fail query immediately if no matching nodes available#12157

Merged
losipiuk merged 1 commit intotrinodb:masterfrom
losipiuk:lo/wait-if-no-nodes
Apr 29, 2022
Merged

Do not fail query immediately if no matching nodes available#12157
losipiuk merged 1 commit intotrinodb:masterfrom
losipiuk:lo/wait-if-no-nodes

Conversation

@losipiuk
Copy link
Copy Markdown
Member

@losipiuk losipiuk commented Apr 27, 2022

Description

Do not fail query immediately if there are no nodes available that match tasks' hard requirements (e.g. expose given catalog).
If such a situation occurs wait for some time and only fail if we still cannot find any matching node.

fixes: #11020

Is this change a fix, improvement, new feature, refactoring, or other?

improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

core

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@losipiuk
Copy link
Copy Markdown
Member Author

CI: #12151

@cla-bot cla-bot bot added the cla-signed label Apr 29, 2022
Do not fail query immediately if there are no nodes available that match
tasks' hard requirements (e.g. expose given catalog). If such a situation
occurs wait for some time and only fail if we still cannot find any
matching node.
@losipiuk losipiuk force-pushed the lo/wait-if-no-nodes branch from cbec9f3 to 8631b00 Compare April 29, 2022 09:31
@losipiuk losipiuk merged commit 34ee3c1 into trinodb:master Apr 29, 2022
@github-actions github-actions bot added this to the 380 milestone Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Wait with timeout instead failing immediately if no candidate nodes available in NodeAllocator

3 participants