Hi Team, Our env : Servers : 3 Cache Configuration : REPLICATED
In one of our clients, the continuous query - Initial query did not return any result during client start whereas it was expected to return a single row. This happened for about 3-4 times over a period of 2 hours. It did return the right result after a couple of restarts. I am trying to debug what happened when it did not return the result . My suspicions are as below : 1. Last week we changed the client communication timeout as below as per the discussion here ( http://apache-ignite-users.70518.x6.nabble.com/IgniteSpiOperationTimeoutException-Operation-timed-out-timeoutStrategy-ExponentialBackoffTimeoutStray-tp34196p34377.html ). Server was already on the below timeout values. : <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi" scope="prototype"> <property name="connectTimeout" value="5000"/> <property name="maxConnectTimeout" value="10000"/> Could it be possible that TcpCommunicationSpi timed out before the results were seen on the client side ? 2. Did the replication between the servers not work ? Is it possible that one of the servers had the wrong value ? How do I debug this ? Please note when I connect to each of the 3 servers using dbeaver, they all return the correct row right now.( Since I got to know of this issue after 2 days, I am not sure what was the row value at the time of this issue ) 3. How do I know which server( out of the 3 servers ) was the client's continuous query -> initial query run on ? How do I debug this further ? regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
