Re: Ignite Load Hangs at the end while using DataStreamer

Hello! I can see that some data processing is happening in thread dumps, but also this: [11:16:11,637][INFO][grid-nio-worker-tcp-comm-2-#26][TcpCommunicationSpi] Accepted incoming communication connection [locAddr=/172.16.1.7:47100, rmtAddr=/10.139.0.10:38624]

Re: Ignite Load Hangs at the end while using DataStreamer

Thanks Ilya. I have changed the Client Side Machine to prefer IPv4 Stack and hence that error went away. But still the data-streamer-stripes and tcp-comm-worker threads keep getting stuck. I am attaching the logs again. (These contain the thread-dump themselves) log.zip

Re: Ignite Load Hangs at the end while using DataStreamer

Hello! I think your problem as follows: [15:09:53,418][WARNING][disco-event-worker-#37][GridDiscoveryManager] Local node's value of 'java.net.preferIPv4Stack' system property differs from remote node's (all nodes in topology should have identical value) [locPreferIpV4=true, rmtPreferIpV4=null,

Re: Ignite Load Hangs at the end while using DataStreamer

Hi I thought I was hitting: (https://issues.apache.org/jira/browse/IGNITE-8564) which got fixed in 2.7. I changed the version to 2.7.6 and retried, but it still does not work. Here are the logs for 2.7.6 1. Logs.zip Here is

Re: Ignite Load Hangs at the end while using DataStreamer

Hi Denis Thank you for the response. Please find the thread-dumps (Had to split it in 3 files since it was large) 1. T1.pdf 2. T2.pdf 3. T3.pdf

Re: Ignite Load Hangs at the end while using DataStreamer

Please attach all the thread dumps and log files for the investigation. - Denis On Wed, Feb 5, 2020 at 8:03 AM pg31 wrote: > Hi > > Cluster Configuration: > 3 Nodes (112 GB Memory / 512 GB Disk) > > Ignite Configuration: > 1. Persistence Enabled > 2. Version: 2.6.0 > 3. Configuration is as

Ignite Load Hangs at the end while using DataStreamer

Hi Cluster Configuration: 3 Nodes (112 GB Memory / 512 GB Disk) Ignite Configuration: 1. Persistence Enabled 2. Version: 2.6.0 3. Configuration is as follows: