Hello Everyone, One of our cache access pattern is that it is accessed beyond an interval of 30 seconds (which is the default connection timeout). Every time it happens the first call to the cache takes a long time to fetch the results.
I am planning to increase the idleConnectionTimeout to a big value (may be a few hours) so that as long as users are active, they can access the system without suffering from long wait every 30 seconds. My question are - 1. Is this approach ok? 2. What are the potential issues with this approach? 3. If the client node (i.e. tomcat) shuts down what happens to the stale connections? What could be the repurcussions if the server node tries to access that cached connection? 4. Does this property (idleConnectionTimeout) needs to be set up only on Ignite server nodes? And not on the Ignite client nodes? We are using Ignite 2.0. Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Large-value-of-idleConnectionTimeout-in-TcpCommunicationSpi-tp15138.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
