Thanks, tried and it seem this issue has been fixed.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp16403p16480.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
x27;s very strange the query fails only when exactly one record is returned
in result set
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp16403.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
.getAll(QueryCursorImpl.java:113)
~[ignite-core-2.0.0.jar:2.0.0]
... 181 more
It's very strange the query fails only when exactly one record is returned
in result set
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp
gnite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp6667p6823.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
In some case the error is "Query was cancelled, client node disconnected".
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp6667p6699.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
tep (used partitoned
cache over 3 nodes):
- tune up the JVM as described in help docs
- increase the max memory size of JVM (server & clinet processes)
- on heap storage/off heap storage
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-q
ough the QueryCursor instead of calling getAll(). If you iterate, Ignite
will fetch data in pages, discarding old ones. So the client will have only
one page at a time in memory and will not fail.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-
