Re: SQL Query full table scan, Node goes down
Hi, Please read the documentation more accurate. The lazy flag you should set on the SqlFieldsQuery object. It could be set on that node where you are going to use it. BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SQL Query full table scan, Node goes down
Thanks Andrew, I want to control on Server node , its hard from client side . Is there anyway I can set this lazy on Server node? Thanks Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SQL Query full table scan, Node goes down
Hi, Try to set Lazy flag for SQL query [1]. [1] https://apacheignite-sql.readme.io/docs/performance-and-debugging#result-set-lazy-load On Tue, Jun 19, 2018 at 8:06 PM bhaskar wrote: > Hi, > I have Ignite 5 node cluster with more than dozen tables(Cache) . Our > client > are using SQL and Tableau. The node goes down when any client quries select > * from table which is bigger than RAM size. > we have 3 years data but last 2 months data is actively quried 80% of time. > > 1. How can I control such SQL when the rows are more than RAM size? > 2. We have to control on the node not client as we can't conrol client. > > Thanks > Bhaskar > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
SQL Query full table scan, Node goes down
Hi, I have Ignite 5 node cluster with more than dozen tables(Cache) . Our client are using SQL and Tableau. The node goes down when any client quries select * from table which is bigger than RAM size. we have 3 years data but last 2 months data is actively quried 80% of time. 1. How can I control such SQL when the rows are more than RAM size? 2. We have to control on the node not client as we can't conrol client. Thanks Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/