how to optimization this

Hi we have Performance testing capabilities for project?? the project build with ignite client config by TcpDiscoverySpi , only one ignite node. we deploy two server machine, one web project with ignite client on serverA,one ignite 2.7.0 on serverB. the opration is get object from ignite.

Duplicate column name while creating table

*I am able to create the table with duplicate column name.* I was expecting some error saying "cannot create table; duplicate column name: NAME" Is there some reason that Ignite is not throwing error/exception OR is it a bug? CREATE TABLE Person(ID INTEGER PRIMARY KEY, NAME VARCHAR(100),

Understanding Write/Read IOPS during Ignite data load through Streamer and JDBC SQL

When we are writing the data to ignite thru streamer ( key, value) and Ignite JDBC ( into couple of SQL tables) we get very high throughput when read IOPS are low and Write IOPS are high and we get very low throughput when Reads and Writes are competing. So my question when I am writing to the

Adhoc Reporting use case (Ignite+Spark?)

Hello, I am trying out Ignite+Spark combination for my adhoc reporting use case. Any suggestion/help on similar architecture would be helpful. Does it make sense or I am going totally south ?? thanks in advance -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Error when we shutdown the node during a rebalance

Hi - I am bumping into the following error frequently and causing the data loss whenever we shutdown the ignite node during data rebalance. I am shutting down the ignite in a safe mode i.e. Ignition.stop(false); Here is the stack trace : Caused by: class

Possible race on node shutdown

Hello, Yesterday we got error on node shutdown while test our system: 2019-12-03 18:49:53,653 [pool-228-thread-1] INFO   r.s.d.m.c.m.PoisonPill:54 - Poison pill works on e45190a6-de52-4e43-b710-1ee8cd1f60a6 2019-12-03 18:49:53,657 [pool-228-thread-1] INFO   r.s.d.m.c.m.ClusterLifecycleBean:61 -

Ignite hanging (dead looping) at TCP discovery stage

Hi, We are running an ignite cluster by TcpDiscoverySharedFsIpFinder. It works well until we installed docker on the machine. After docker is installed, docker created a NAT Ethernet adapter vEthernet (DockerNAT): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . :