[ 
https://issues.apache.org/jira/browse/IGNITE-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-9141:
------------------------------------
    Description: 
One of mandatory steps of SQL query execution is topology mapping - we need to 
select nodes where required caches are located, and make sure that their 
partition distribution is valid for the given SQL query. Once nodes are 
detected, we try to reserve partitions of interest on mapper nodes to make sure 
that they will not be evicted during query execution. 

However, mapping step may fail for many reasons. Most often this is rebalance 
or concurrent node failures. In this case we simply retry the whole query 
execution from scratch. In IGNITE-9114 we ensured that retry cycle is not 
infinite and that root cause of remap is logged. However, original root cause 
of remap is not propagated to client node making the problem hard to debug for 
end users. Also we do not have enough tests for remap events. Let's fix this.

> SQL: Trace and test query mapping problems
> ------------------------------------------
>
>                 Key: IGNITE-9141
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9141
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.6
>            Reporter: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.7
>
>
> One of mandatory steps of SQL query execution is topology mapping - we need 
> to select nodes where required caches are located, and make sure that their 
> partition distribution is valid for the given SQL query. Once nodes are 
> detected, we try to reserve partitions of interest on mapper nodes to make 
> sure that they will not be evicted during query execution. 
> However, mapping step may fail for many reasons. Most often this is rebalance 
> or concurrent node failures. In this case we simply retry the whole query 
> execution from scratch. In IGNITE-9114 we ensured that retry cycle is not 
> infinite and that root cause of remap is logged. However, original root cause 
> of remap is not propagated to client node making the problem hard to debug 
> for end users. Also we do not have enough tests for remap events. Let's fix 
> this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to