Hello! After more investigation we have opened a new ticket: https://issues.apache.org/jira/browse/IGNITE-10580 And the workaround is different: you need to make query non-local, for example by turning cache partitioned instead of replicated. If you execute two identical local queries (ones that query planner considers such) you will get into such problems.
You can also drop lazy=false for now. Regards, -- Ilya Kasnacheev пт, 7 дек. 2018 г. в 06:56, yangjiajun <1371549...@qq.com>: > Hello! > > Please fell free to deal with the code. > > I try to add where clause to my query,but it does not save me.The test code > still throws the exception after a while.My ignite's version is 2.6.Does > the > workaround work in latest version?Or does this workaround only reduce the > probability of the issue? > > > ilya.kasnacheev wrote > > Hello! > > > > I have confirmed this problem and we are working on it in > > https://issues.apache.org/jira/browse/IGNITE-9171 > > I have converted your reproducer to Ignite test, hope you don't mind. > > > > There is a workaround in that you could add a parameter to your query, > > such > > as WHERE id > ?, and pass something like -1 to bind to this parameter, > > which should prevent the issue from occurring. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 5 дек. 2018 г. в 16:21, yangjiajun < > > > 1371549332@ > > >>: > > > >> Hello. > >> > >> I test setQueryTimeout method to see whether it works or not because I > >> try > >> to prevent long time queries from blocking other operations.According to > >> my > >> test,this method has no effect.You can also see that I have already > >> removed > >> it in my latest test code.The code is simple and reproduce my issue. > >> > >> > >> Hello! > >> > >> Why do you have setQueryTimeout here? What happens if you take it off? > >> > >> Regards, > >> -- > >> Ilya Kasnacheev > >> > >> > >> ср, 5 дек. 2018 г. в 09:17, yangjiajun <1371549332@>: > >> > >> > >> > >> > >> -- > >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > >> > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
