Comments (4)
Yes, we should.
Several considerations remain:
- Handling forward failures.
- Determining the layer for forwarding: Should it occur in the HTTP handler or at a lower level?
from databend.
Do we need to consider failure? sql callers need to know clearly whether sql execution succeeds or fails.
If forwarding fails and returns execution fails, but the actual sql is still executing, it will cause confusion.
from databend.
some sugesstion:
The forwarding path should not change if the number of query members changes(in process of scale-in or scale-out).
If the client side gets SQL execution failure, then it must really fail, no matter on any node.
from databend.
Here's a condensed version of the protocol:
- Client sends a request to query-1 (warehouse-id: w1).
- Client sends the next request to query-2 (warehouse-id: w2), including a header with the previous warehouse-id (w1).
- Query-2 responds with a forward protocol(reponse with query-1 host?), instructing the client to redirect the query to query-1.
- Client redirects the query to query-1.
- Client receives the result from query-1.
This protocol ensures that the client interacts with the correct query node based on the previous request's warehouse-id, maintaining consistency and safety in a 3-node cluster.
I am not sure this works in k8s, please clarify, @ZhiHanZ
from databend.
Related Issues (20)
- bug: copy into table source can't contain window|aggregate|udf|join functions HOT 1
- copy into use specified file list is very slow
- Tracking: refactor and optimize `merge into`
- increase `default_wait_time_secs` to be 10 secs HOT 1
- Feature: Sort aggregation support
- bug: Error when create table have column name have upper character HOT 3
- feat: support warehouse-level settings
- bug: use purge=true in copy into with failed ,but file was delete HOT 1
- Feature: copy into table support `on_error = skip_file`
- tracking: inverted index benchmark HOT 2
- bug: invalid unicode code point when loading files dump with format ndjson.
- bug: tuple field with special char will cause session panic HOT 1
- bug: create user with DEFAULT_ROLE must uppercase HOT 1
- Tracking: Multi-table insert statement
- Feature: SeaTunnel integration
- bug: Unable to get field named "5". Valid fields: ["2", "3", "10"] HOT 1
- Inconsistency between code and documentation HOT 1
- feat: add query digest to query_log
- bug: no overload satisfies `cosine_distance(Array(Float32 NULL) NULL, Array(Float32))` HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from databend.