Re: GridCachePartitionExchangeManager Null pointer exception

Hello Pavel, OK. The place where I am a little bit not clear is on your below previous comment As a workaround, I can suggest to not explicitly declare caches in the client configuration. During joining to cluster process, the client node will receive all configured caches from server nodes

Re: nodes are restarting when i try to drop a table created with persistence enabled

Shivakumar's system configuration and mine could be different. But I feel, we are seeing the same issue here. Deleting tables via a single thick client causes other thick clients to go out of memory. This OOM issue was reported below here. http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-

Re: nodes are restarting when i try to drop a table created with persistence enabled

Hello, please ignore the below comment on this topic >>> https://issues.apache.org/jira/browse/IGNITE-12255 Upon reviewing 12255, the description of this issue shows an exception occurring on the thick client side. However, the logs, that I attached show a null pointer exception on the ALL the se

Starvation in striped pool

hi, We are seeing a crash of the server node. This is with Ignite 2.7.6 Any insight and a possible workaround would be deeply appreciated? attached is the log ignite-29268843.zip * [11:16:09,531][WARNING][grid-ti

Re: Starvation in striped pool

OK. There could have been a temporary network issue between the server and client node. However, I was expecting the server node to throw the client out of the cluster and resume normal functioning. But what bothers me is that the server node never recovered after the network issue and finally got

Re: Starvation in striped pool

Hello Ilya Once connection goes bad between client and server, which configuration parameter on the thick client-side would force stop the thick client from pinging server... Tried join timeout, connection timeouts, in communicaiton and discovery spis and nothing ever worked. Have seen in a few

Re: Starvation in striped pool

Attached are the logs. In the server log, you will see the thick client continuously pinging server indefinitely...there is no recovery of the thick client. SO, the problem is, we can't even reboot the thick client in a production scenario, as it does even fail (meaning, the configured failure hand

Re: Starvation in striped pool

Ilya. What is most mysterious to me is, I disabled reconnect of think client (clientReconnectDisabled=true). Still the server prints, the below, where the same thick client is making an immediate attempt to reconnect back to the cluster, while the previous connecting isn't still successful. [0

Re: Starvation in striped pool

>>I'm almost certain is that problem is that server node cannot open a connection to client node (and while it tries, it will reject connection attempts from client node) The default idleTimeout of TCP communication spi is 6 minutes. So I assume, after this timeout, the connection is closed and re

Re: GridCachePartitionExchangeManager Null pointer exception

Pavel, are ignite 2.7.6 binaries built with assertions disabled? THis could explain the null pointer exception seen here on the server-side. I am still not following if the null pointer exception, that I am reporting here is understood and if there is a defect filed for this -- Sent from: http:/