mirror of https://github.com/citusdata/citus.git
c760cd3470
* Move local execution after the remote execution
Before this commit, when both local and remote tasks
exist, the executor was starting the execution with
local execution. There is no strict requirements on
this.
Especially considering the adaptive connection management
improvements that we plan to roll soon, moving the local
execution after to the remote execution makes more sense.
The adaptive connection management for single node Citus
would look roughly as follows:
- Try to connect back to the coordinator for running
parallel queries.
- If succeeds, go on and execute tasks in parallel
- If fails, fallback to the local execution
So, we'll use local execution as a fallback mechanism. And,
moving it after to the remote execution allows us to implement
such further scenarios.
|
||
|---|---|---|
| .. | ||
| adaptive_executor.c | ||
| citus_custom_scan.c | ||
| directed_acyclic_graph_execution.c | ||
| distributed_execution_locks.c | ||
| distributed_intermediate_results.c | ||
| insert_select_executor.c | ||
| intermediate_results.c | ||
| local_executor.c | ||
| multi_client_executor.c | ||
| multi_executor.c | ||
| multi_server_executor.c | ||
| partitioned_intermediate_results.c | ||
| placement_access.c | ||
| query_stats.c | ||
| repartition_join_execution.c | ||
| subplan_execution.c | ||
| tuple_destination.c | ||