Hi, I want to discuss about potential memory leak in Ignite (I imply potential mem leak as I'm not 100% sure I do something wrong ;))
However, believe I found a corner case which triggers memory leak even with the lates stable version. In my case, MapQueryResults fills MapNodeResults map without being removed which leads to out of memory exception or huge gc major collections. I'm pretty sure the issue is in *fetchNextPage* method of MapQueryResult class as this method never returns *true* if you have result set with pageSize*n records. Actually, we had a major issue with memory in our production cluster and the only workaround was to limit all queries bellow page size (currently 1024). Regards, Igor -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
