no data by JDBC or Cache query!

Ignite 2.7.0 I poured data by the following code, but I didnt get data after executing jdbc or cache query, while I just can see data by "cache -scan -c=@c4" by the command window: IgniteVisorCmd.sh. why? IgniteCache personCache = igniteClient.cache("PersonCache"); Person person = new Person(); p

thread number tradeoff

Hi guys. My case scenario: Ignite 2.3, multi servers with 16 core CPU and 192G memory. The cluster mode is multi-node per server. according to this doc (https://apacheignite.readme.io/docs/thread-pools), default thread number (max(8, total number of cores)) of all thead pools is 16. For bette

how to set SQL timeout for the cluster?

Hi igniters, we want to avoid long query SQL running in the cluster, thus we need setup unified SQL timeout in the XML configuration file. but I didn't find related properties or beans. how? thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cluster hanged when client node put data into the caches

@Nikolai Your suggestion is right. "to-space exhausted" occured in GC Logs on 3 out of 6 server nodes, as: Node 1: 2017-12-05T18:36:48.716+0800: 6870.705: [GC pause (G1 Evacuation Pause) (young), 0.4171797 secs] [Parallel Time: 412.1 ms, GC Workers: 13] [GC Worker Start (ms): Min: 6870705

Re: cluster hanged when client node put data into the caches

thread dump: Attaching to process ID 12837, please wait... Debugger attached successfully. Server compiler detected. JVM version is 25.65-b01 Deadlock Detection: No deadlocks found. -

Re: cluster hanged when client node put data into the caches

@Nikolai thank you for your response. some error in client node: 2017-12-06 13:35:03.721 -ERROR 9688 [order] com.a.u.IgniteAffinityHelper : error: org.apache.ignite.IgniteClientDisconnectedException: Client node disconnected: null at org.apache.ignite.internal.GridKernalGatewayIm

cluster hanged when client node put data into the caches

Hi guys. our project was stunned into this critical issue. Ignite version 2.2, 10 nodes on 5 servers. Client node consumed data from Kafka, and put them into caches. Sometimes client node was disconnected suddenly, then the cluster with 10 server nodes hanged, CPU usage on 5 servers reached almost

query operator in local node

Hi Igniters, Ignite 2.2, a couple of server nodes. I need to realize cache query operator only in local node or specific node, but I didn't found the related API in IgniteCache. I appreciate if you could give me a hint. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client load balancing and failover support

Client node driver mode could bring a huge memory usage on your application ( local cache) thus I believe most choose JDBC thin driver mode. BTW our data source library called Druid doesn't support common JDBC Driver, which reported transaction issues. So, this feature seems very important for

Public thread pool idle number is always 0 ?

hi Ignite version 2.2, 14 nodes based on 7 cloud servers with 16 cores. when running, I found Public thread pool idle numbers on every node is always 0. Initially, I changed the configuration "publicThreadPoolSize" from 64, 128, then 256 now. The CPU usage is not high , average 20-30%. how to s

Custom Expiry Policies ?

Hello guys. a tough task comes. As you know every entity is created at different moment. After I load them into the Cache, I hope they have different expiry duration in the cache. give me a hint to realize Custom Expiry Policies, thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble

Re: what's best practice of “in” operator?

Thank @ezhuravlev. Following the above document, I tried it with: SELECT p.* FROM "personCache".Person p join "OrganizationCache".Organization(area String =('london','paris','roma',...)) o on p.org_id = o.id But It failed, the error log was like : Failed to parse query Caused by: org.h2.

what's best practice of “in” operator?

Ignite 2.2： common sql: select p.* from "personCache".Person p join "OrganizationCache".Organization o on p.org_id = o.id where o.area in ('london','paris','roma',...) Is there the better sql from performance perspective? thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.

what did this log indicate?

those logs was from the node (192.168.34.189), which accepted a ton of incoming communication connection frequently. Are there some errors occured in this node? how to handle this? thanks. [20

Does ignite-schedule not upgrade after 2.1.0?

-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/