Re: Too many TCP discovery accepted incoming connections

HI Ilya, Please find attached full log file. Regards, Gangaiah server_log.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Too many TCP discovery accepted incoming connections

Hi Ilya, There is no jvm pause, only one entry in the server log but that too after affect. The incoming connections started at 2021-04-21T14:52:50,035 and jvm pause could see at 2021-04-21T14:54:18. I have attached logs file, could you please check. [2021-04-21T14:54:18,035][WARN

Too many TCP discovery accepted incoming connections

Hi Igniters, Some times we are seeing too many 'tcp discovery accepted incoming connections' from client servers in server logs. Is it due to network glitch or connectivity break between servers and clients?. This leads to system critical errors and many clients disconnected and reconnected.

Re: Logging client instance name in server logs

HI, Anyone please help us, how to log the client instance name in server logs. Regards, Gangaiah -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Logging client instance name in server logs

Hi Igniters , We have 300 plus clients connected to cluster, some times need to know which client connected or left or connection established. Could see only node-id in serverlogs, not able to find specific client. Want to log client name( client ignite instance name set client side) in server

Re: partition-exchanger system-critical thread blocked

Hi Ilya, Our server nodes not running in kubernetes, so we have simple ignite cluster no relation to kubernetes. But we have few clients which running inside kubernetes cluster and few clients are out side kubernets, both are connecting to same ignite cluster. - Thanks and Regards,

Re: partition-exchanger system-critical thread blocked

Hi Ilya, We are using 2.7.6 version, is it available in the version. And also, the clients which are running in kubernetes able to connect to the cluster. Sometimes facing the issue whenever we restart the multiple clients/adding multiple clients to cluster and suddenly sometimes the error

Re: partition-exchanger system-critical thread blocked

Hi Ilya, We are using 2.7.6 version, is it available in the version. Thanks and Regards, Gangaiah - Thanks and Regards, Gangaiah -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: partition-exchanger system-critical thread blocked

Hi Ilya, We have configured atomictyMode 'ATOMIC' for all caches it's not transactional, below is our cache configuration for one of the caches. ### Cache Configuration I

Re: partition-exchanger system-critical thread blocked

Hi Ilya, Again we got same issue 'tcp-comm-worker-#1' blocked. We have observed one thing whenever multiple clients joining to cluster at same time, the error is printing. I could see there is only one thread(tcp-comm-worker), checked from logs and also from visualvm. >From documentation also,

Re: partition-exchanger system-critical thread blocked

Hi Ilya, Regarding exchange worker, the jira saying that 2.8.1 and 2.9 but we are using 2.7.6 version. So it could be in 2.7.6 as well. But still I am not understanding here is, there is no node join/left or cluster activation or cache creation near to the error logging time. Don't know why PME

Re: partition-exchanger system-critical thread blocked

Hi Ilya, Please find attached entire log file. Regards, Gangaiah 18.zip - Thanks and Regards, Gangaiah -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteC++ throughput

Hi Lieuwe, To understand this in detail, please give more details like how you are calculating TPS and code snippet for each one where you are doing put/get/cursor.hasNext(). Regards, Gangaiah - Thanks and Regards, Gangaiah -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: partition-exchanger system-critical thread blocked

HI Ilya Kasnacheev, Below are log entries with the tread name 'partition-exchanger' Line 41311: [2020-11-09T06:44:13,605][ERROR][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Blocked system-critical thread has been detected. This can lead to cluster-wide undefined

tcp-disco-msg-worker system-critical error

Hi Igniters, Sometimes below system-critical error printing in the production logs whenever restart the clients. [2020-11-09T02:31:24,733][ERROR][tcp-disco-msg-worker-#2%EDIFCustomerCC%][G] Blocked system-critical thread has been detected. This can lead to cluster-wide undefined behaviour