[ 
https://issues.apache.org/jira/browse/IGNITE-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703236#comment-16703236
 ] 

Yury Gerzhedovich commented on IGNITE-6173:
-------------------------------------------

[~vozerov], 
 # Yes, you are right. Removed it together with invocatin 
initDistributedJoinMessaging() during creation of client index.
 # If it will be extracted then it need to add fake return statement  for each 
methods. I've extracted the exception into constant and use the constant for 
each such methods.
 # Many thanks for the point. It was really bug. I've added start caches and 
test for such case.
 # Agree. Fixed.
 # Ok.
 # Removed.
 # Yes, agree. Fixed.
 # Fixed.

I've started test and waiting to get Bot visa. 

Please check my last changes.

> SQL: do not start caches on client nodes
> ----------------------------------------
>
>                 Key: IGNITE-6173
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6173
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: sql-stability
>             Fix For: 2.8
>
>
> When cache is started, this even is distributed through custom discovery 
> message. Server nodes start the cache, client nodes do nothing until cache is 
> requested explicitly. At the same time H2 database objects are created only 
> when cache is really started. 
> For this reason query parsing could lead to {{TABLE NOT FOUND}}, {{INDEX NOT 
> FOUND}}, etc. errors. If such exception is observed, we force start of all 
> known cache on a client and then retry. See 
> {{GridCacheProcessor#createMissingQueryCaches}} method. 
> First, client node cache start leads to another custom discovery message. So 
> query performance may suffer. Second, this is not needed! We already have all 
> necessary cache info in discovery. 
> Let's try to find a way to use available discovery data and do not start 
> cache on a client for SQL query execution.



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

Reply via email to