You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "James (JIRA)" <ji...@apache.org> on 2019/05/09 14:47:00 UTC

[jira] [Created] (IGNITE-11842) clients fails to connect

James created IGNITE-11842:
------------------------------

             Summary: clients fails to connect
                 Key: IGNITE-11842
                 URL: https://issues.apache.org/jira/browse/IGNITE-11842
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 2.7
         Environment: kubernetes

 
            Reporter: James


The main symptom is that clients are failing to connect to the ignite cluster, with reported timeouts in the logs.

The main fact we have is this (from within the client within a kubernetes container on Linux):

/ # netstat -ntp

Active Internet connections (w/o servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

tcp   215796      0 ::ffff:10.42.2.97:43666 ::ffff:10.42.3.170:47500 ESTABLISHED 13/java

 

Namely, the application is failing to read data from the tcp socket. Notice the “Recv-Q” of 215796.

 

This could be an client application, but also the same thing happens with ignitevisor.sh

Downgrading to Apache Ignite 2.3 resolves the problem.

Testes so far:

2.7  intermittently fails to connect to the ignite cluster.

2.3 seems OK.

2.6 not yet tested.

 

Has anyone else seen this?

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)