Re: High number of Exception Unexpected response ID with setTimeout

[Ilya Kasnacheev]

Hello!

I have filed a ticket: https://issues.apache.org/jira/browse/IGNITE-13498

Regards,
-- 
Ilya Kasnacheev


пн, 28 сент. 2020 г. в 12:02, AravindJP :

> We are seeing high number of exceptions after setting setTimeout() in
> ClientConfiguration
> any idea what's the reason for this ? Exception: Unexpected response ID
> [3630521808404506928], [5259] was expected
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:160)
>
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:126)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.getAll(TcpClientCache.java:165)
>
> We set timeout as mentioned below
> ClientConfiguration cfg = new ClientConfiguration().setAddresses(IP:PORT);
> cfg.setTimeout(50);
> IgniteClient ignite = Ignition.startClient(cfg);
> --
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>

Re: High number of Exception Unexpected response ID with setTimeout

[Andrei Aleksandrov]

Hi,

It will be great to take a look at full logs that contain these errors.

BR,
Andrei

9/28/2020 12:35 PM, AravindJP пишет:

Thank you stepan for your reply , problem is the parent thread calling ignite
cache get has a timeout of 120 ms , hence we allow a max of 100 ms for every
cache read . We are seeing that during non peak time , 80% of cache read is
< 20 ms only . But during peak load application is crashing with some
threads going beyond 400 to 500 ms . That's the reason why we had to limit
timeout to 50 . But why such an exception occurs ? Why such an exception
occurs from Ignite side ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: High number of Exception Unexpected response ID with setTimeout

[AravindJP]

Thank you stepan for your reply , problem is the parent thread calling ignite
cache get has a timeout of 120 ms , hence we allow a max of 100 ms for every
cache read . We are seeing that during non peak time , 80% of cache read is
< 20 ms only . But during peak load application is crashing with some
threads going beyond 400 to 500 ms . That's the reason why we had to limit
timeout to 50 . But why such an exception occurs ? Why such an exception
occurs from Ignite side ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: High number of Exception Unexpected response ID with setTimeout

[Stephen Darlington]

50ms isn’t very long. I’d recommend at least a few seconds, maybe 5000 rather 
than 50.

Regards,
Stephen

> On 28 Sep 2020, at 10:01, AravindJP  wrote:
> 
> We are seeing high number of exceptions after setting setTimeout() in 
> ClientConfiguration 
> any idea what's the reason for this ?
> 
> Exception: Unexpected response ID [3630521808404506928], [5259] was expected 
> at 
> org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:160)
>  
> at 
> org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:126)
> at 
> org.apache.ignite.internal.client.thin.TcpClientCache.getAll(TcpClientCache.java:165)
>  
> We set timeout as mentioned below
> ClientConfiguration cfg = new ClientConfiguration().setAddresses(IP:PORT); 
> cfg.setTimeout(50); 
> IgniteClient ignite = Ignition.startClient(cfg); 
> Sent from the Apache Ignite Users mailing list archive 
>  at Nabble.com.

High number of Exception Unexpected response ID with setTimeout

[AravindJP]

We are seeing high number of exceptions after setting setTimeout() in
ClientConfiguration 
 any idea what's the reason for this ?
Exception: Unexpected response ID [3630521808404506928], [5259] was expected
at
org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:160)
  
at
org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:126)
   at
org.apache.ignite.internal.client.thin.TcpClientCache.getAll(TcpClientCache.java:165)
   
We set timeout as mentioned below
ClientConfiguration cfg = new ClientConfiguration().setAddresses(IP:PORT); 
cfg.setTimeout(50); 
IgniteClient ignite =   Ignition.startClient(cfg);



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/