Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hello! I have no idea, I recommend collecting a heap dump and analyzing it to locate any leaks. I think that something would indeed happen at the cluster in that time. Regards, -- Ilya Kasnacheev пт, 21 февр. 2020 г. в 06:07, wentat : > Hi Ilya, > > at the time of running the experiments in t

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hi Ilya, at the time of running the experiments in the logs, there was no queries running in the background. Just 30 servers and no clients. What could have caused such high heap usage? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hello! For example, you can do a SQL request with large result set, such as SELECT * without WHERE clause, which may cause server node to run out of memory. Regards, -- Ilya Kasnacheev чт, 20 февр. 2020 г. в 06:23, wentat : > Hi Ilya, > > Thank you for your response. I have checked my client

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hi Ilya, Thank you for your response. I have checked my client side load testing library (I am using YCSB btw) and I found a potential memory leak. However, can the client side using too much heap cause the server to fail? There is no other applications running on the Apache Ignite servers -- S

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hello! >From this log: [17:19:09,949][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible too long JVM pause: 1405 milliseconds. [17:19:12,237][WARNING][jvm-pause-detector-worker][IgniteKernal] Possible too long JVM pause: 1983 milliseconds. [17:19:14,416][WARNING][jvm-pause-detector-worke

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hi Ilya, Thank you for your reply. I have done this test a few times and I consistently get stalling grids during failover/scaling/server swapping I have tried tuning some parameters, according to ignite production prep docs . I ha

Re: Null Pointer Error in GridDhtPartitionsExchangeFuture

Hello! Better issue TERM (kill without -9) so that node can at least gracefully shutdown its file descriptors. Otherwise, the first error looks like some one-off bug, and "Operation has been cancelled (node is stopping)." are self-descriptive and normal. Unfortunately we would need to take a loo