Re: Memory leak.Ignite runs slower and slower after a period of time.

Hi, > Does it mean the cursor still not closed in Ignite-2.6.0? Yes, it seems so. Thanks, S. чт, 11 апр. 2019 г. в 15:06, Justin Ji : > Emmm, Does it mean the cursor still not closed in Ignite-2.6.0? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Memory leak.Ignite runs slower and slower after a period of time.

Emmm, Does it mean the cursor still not closed in Ignite-2.6.0? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hi, > BTW, I can not find the class you provided(Ignite-2.6.0), do you spell it correctly? Oops :) That class was added recently. Please take a look at https://issues.apache.org/jira/browse/IGNITE-10827 The fix is already available on the master branch Thanks, S. чт, 11 апр. 2019 г. в 14:10, Jus

Re: Memory leak.Ignite runs slower and slower after a period of time.

Slava - Thank you again for your reply, I will close the cursor explicitly. BTW, I can not find the class you provided(Ignite-2.6.0), do you spell it correctly? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hello, > I would like to know will resource be closed after I iterate over the Cursor? Well, the answer is yes, the cursor will be closed (the underlying iterator is wrapped by org.apache.ignite.internal.processors.cache.AutoClosableCursorIterator). Please take into account that this behavior is i

Re: Memory leak.Ignite runs slower and slower after a period of time.

One more question. According to the org.apache.ignite.cache.query.QueryCursor.getAll API, I know that the resources will be closed automatically since all results are fetched. I would like to know will resources be closed after I iterate over the Cursor？ The reason why I ask this question is th

Re: Memory leak.Ignite runs slower and slower after a period of time.

One more question. According to the org.apache.ignite.cache.query.QueryCursor.getAll API, I know that the resources will be closed automatically since all results are fetched. I would like to know will resources be closed after I iterate over the Cursor？ The reason why I ask this question is th

Re: Memory leak.Ignite runs slower and slower after a period of time.

Slava - Thank for your reply, I will confirm it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hello, At first glance, your code does not close FieldsQueryCursor instances. Could you explicitly close the cursors via close() or use try-with-resources statement. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/FieldsQueryCursor.html [2] https://ignite.apach

Memory leak.Ignite runs slower and slower after a period of time.

When my Ignite clients run for a while, it becomes slower and slower, and the outputs can be seen in our gc logs: 2019-04-10T06:42:47.885+: 62271.788: [Full GC (Ergonomics) [PSYoungGen: 1494016K->1494005K(1797120K)] [ParOldGen: 2097006K->2097006K(2097152K)] 3591022K->3591012K(3894272K), [Met