[IGNITE-11842] clients fails to connect

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7
• Component/s: cache

Environment

kubernetes

 

• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: James
• Created: 09/May/19 14:46
• Updated: 15/May/19 06:56

Description

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 also fails after a number of clients have connected successfully.

 

Has anyone else seen this?