We are also facing a similar issue where complete cluster behaves like frozen
with cache get time > 200 ms , unable to figure out the root cause . I was
expecting that ClientConfiguration.setTimeout() will work for get read
timeout
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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
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
Hi ,
I am getting below exception after running an Ignite client running
continuously for 48 hrs . My client is running on java (spring boot) . I am
using singleton instance of IgniteClient object to connect and persist
data.
Ignite version 2.8.0
020-08-04 10:02:18.520 ERROR 1 ---
I have Kubernetes Cluster (on GCP) with Apache 2.8.1 (upgraded from 2.8.0 )
with Gridgrain Control center installed. For last 1 weeks Ignite cluster
has 0 load (no read/write request to cluster) . But I am seeing below
exception in my cluster node with lot of threads in TIMED_WAITING, WAITING
In this case , i am trying to connect to a kubernetes cluster remotely .
Using same IP , i am successfully able to put and get data via 10800
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Stephen, i was using IgniteConfiguration to connect , please find below
the full code
Ignition.setClientMode(true);
ClientConnectorConfiguration cfg=new
ClientConnectorConfiguration() .setHost("xx.xx.xx.xx")
Hi ,I have setup a Ignite cluster in google cloud following document :
https://apacheignite.readme.io/docs/google-cloud-deployment. My Ignite
client code which connects to 10800 works fine . ie//THIS WORKS
!!ClientConfiguration ccfg = new