Ignite Cluster getting stuck when new node Join or release

I have 3 node cluster with 20+ client and it's running in spark context.Initially it working fine but randomly get issue whenever new node i.e. client try to connect with cluster.The cluster getting inoperative.I have got following logs when its stuck.If I restart any Ignite server explicitly then

Re: The thread which is inserting data into Ignite is hung

Hi All, We have identified the following issues and fixed after that onwards we haven't got any issue. 1. Cursor is not closed when we do a query 2. backups 2147483646 to 1 or 2 [ i am not sure will it really cause any issue or not.] 3. TCP port 9090 is opened from client to server but not opened

Re: Session.removeAttribute is not working as expected

Hi, 1. Could you please clarify what exactly doesn't work as expected? Does session.attributeNames() result include removed attributes? 2. JAVA_HOME=/opt/java/jdk-10.0.1 - I'm not sure that Apache Ignite was tested on Java 10. Could you try to reproduce the issue on JDK8? 3. Could you share a

Re: Agent not able to connect

Hi Humphrey, Currently, front-end is included into back-end container as static files (html, js). This way we don't have to open two ports. 80 is fully enough. 3001 isn't used now. Regarding documentation, we don't have that one for web agent docker image because it isn't public yet. I hope it

Ignite client mvn artifact's purpose?

Hi Folks, I notice there is a mvn artifact with artifact id "ignite-clients". What is its purpose? https://mvnrepository.com/artifact/org.apache.ignite/ignite-clients/2.4.0 Thanks Muthu -- Sent from:

Affinity colocation and sql queries

Hi All, I'm not sure to have well-understood Ignite affinity colocation. I have several questions. 1/ Does sql queries benefit from affinity colocation? 2/ The use case is an sql query like : SELECT SUBSET1.KEY AS SET1_KEY, SUBSET2.KEY AS SET2_KEY FROM WHOLESET AS SUBSET1, WHOLESET AS