Re: Use IgniteQueue in client

ticket https://issues.apache.org/jira/browse/IGNITE-6437 already created Hi, I want to create an IgniteQueue on a server node and get a reference to this queue on a client node. I get a null pointer exception on client when I do this. This has been asked before in a very old thread and

Re: No heap cleanup on oldest node

You should provide more information. What is your configuration? How do you use the cluster (data, compute, services, ...)? What is consuming memory? Did you try to analyze GC logs and heap dumps? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Spring xml for connecting to Oracle database

Easiest way is to generate all required configuration using Web Console tool: https://apacheignite-tools.readme.io/docs/automatic-rdbms-integration -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Error serialising arrays using Ignite 2.2 C# client

Thanks Alexey. -Original Message- From: Alexey Popov [mailto:tank2.a...@gmail.com] Sent: Tuesday, November 14, 2017 5:09 AM To: user@ignite.apache.org Subject: Re: Error serialising arrays using Ignite 2.2 C# client Hi Raymond, You are right. True multidimensional arrays are not

Spring xml for connecting to Oracle database

Hi, Do we have a sample of the spring xml file to connect to Oracle and perform a "Read-through" operation? Ganesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

No heap cleanup on oldest node

Hi, there 10 Ignite Cluster were configured. When one of these nodes increased the CPU utilization, the Heap continued to grow after the Minor GC. Then he died after Full GC. What is the cause? :( -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Use IgniteQueue in client

Thanks Alexey. I think the problem is that Ignite.queue and Ignite.set javadocs mention that null is an acceptable entry and also suggest that null can be used when we do not want to create a new set or queue. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Continuous update Data Grid Cache

Hi, To avoid any downtime here I would recommend to load the new data set in the same cache and remove the old entries from there once the preloading is finished. This approach assumes that both old and new entries can co-exist in the cache. — Denis > On Oct 23, 2017, at 7:13 AM, blackfield

Re: Ignite 2.3.0 hangs in startup

Hi, After enabling debug mode on ignite logging, the log shows ignite continuously getting timeout in the following: - 2017-11-13 21:33:00.770 DEBUG 11232 --- [r-#23%bfs-grid%] o.a.i.i.p.timeout.GridTimeoutProcessor : Timeout has occurred [obj=CancelableTask

Re: Error serialising arrays using Ignite 2.2 C# client

Hi Raymond, You are right. True multidimensional arrays are not supported now in binary serialized (C#). Jugged arrays work fine. So, you can use them or just one-dimensional array with 2D-index calculation. Anyway, I opened a ticket: https://issues.apache.org/jira/browse/IGNITE-6896 You can

Re: Adding more ignite-clients slows down the first client

Hi Tobias, if you need to do an initial loading of a big amount of data, please read the following section: https://apacheignite.readme.io/docs/streaming--cep >BUT when I add one more client to try to increased (scale horizontally) >I clearly see that the INSERT speed decreases on the first

Re: Trouble with v 2.3.0 on AIX

Logs uploaded. Node1 started first. Node2 couldn't join the cluster. Search for first "java.lang.IllegalArgumentException: null" in node2.log node1.zip node2.zip

Re: Use IgniteQueue in client

Created https://issues.apache.org/jira/browse/IGNITE-6889 (ignite.queue() returns null when queue configuration is null)

Re: Use IgniteQueue in client

Hi, Two things: 1. You must use same configuration (limit and CollectionConfiguration) on both client and server 2. You cannot pass "null" as CollectionConfiguration. Pass empty CollectionConfiguration (new CollectionConfiguration()) if you have no specific settings. This code

Re: Computation best practices

hi @luqmanahmad I was thinking about it as well a little bit in my project... and I'm not sure if the cluster group is the best direction here. One way to think (probably) about efficient resource usage is to bring job stealing into your cluster. In this case you do a "default" setup where data

Re: Computation best practices

Hi Christos, Thanks for getting back to me. There is no specific need for it - I am just trying to get my head around for the best practices in that case data nodes does make sense to me to perform the computation. To be honest just a bit confused with the Cluster groups and trying to find a

Use IgniteQueue in client

Hi, I want to create an IgniteQueue on a server node and get a reference to this queue on a client node. I get a null pointer exception on client when I do this. This has been asked before in a very old thread and is reportedly fixed as per this issue

Re: Computation best practices

Hi Luqman, Is there a specific reason why you want to keep the data nodes separate from the compute nodes? As you say this beats the point of collocation. You should use the data nodes for compute and ensure you have a way to monitor and kill spurious tasks that may be executed on the grid.

Computation best practices

Hi there, Just trying to clarify few bits in my head around data nodes and compute nodes. Let's say we have 10 data nodes which are solely storing the data using affinity collocation and we have 10 compute nodes as well for computing different tasks on the cluster. Now we know that if we want

Re: Error when deploying a service into an Ignite cluster

Hi, Would you please share a stacktrace? Looks like an error occurs while service deployment was in progress. On Mon, Nov 13, 2017 at 5:44 AM, Raymond Wilson wrote: > I have made a simple C# service in Ignite 2.2. When I deploy it, like this: > > > >

Cluster nodes failures while under load

Hello, I have a pretty vague description for the problem I am having with my Ignite cluster and I was wondering if anyone is experiencing similar behaviour. I am holding an in-memory database on an Ignite cluster, with about 500 GB of data in it (across 3 nodes). Data is constantly being streamed

RE: Node failed to startup due to deadlock

Ups, there is a some issue with text formatted below. It should be just a replace  cache2.lock("fake"); with  Lock lock = ignite0.reentrantLock("fake", true, false, true); where ignite0 is a "final" copy for a new Thread  final Ignite ignite0 = ignite; Thank you, Alexey From: Alexey Popov Sent:

RE: Node failed to startup due to deadlock

Hi Naresh, I still don't have a clear understanding of your case. Very probably you just need a Cache Store with Read-Through enabled. Please have a look at [1] and Cache Store examples. As for code provided - you can have a workaround here until

Prohibit "Node is out of topology"

Hi, pretty randomly we discover that certain ignite nodes shutdown without a reasonable outer cause. The grid was not in use the time this happened (no load on the system): 2017-11-11 06:06:26:752 + [grid-timeout-worker-#23] INFO org.apache.ignite.internal.IgniteKernal - Metrics for local

Re: Problem with spring-data-commons 2

Hi, Apparently you cannot just bump the Spring dependency due to that new deleteAll(Iterable ids) they added in CrudRepository 2.0 that conflicts with the same method in our IgniteRepository. I opened a tickets to support Spring 2.0: https://issues.apache.org/jira/browse/IGNITE-6879

RE: write behind performance impacting main thread. Write behindbuffer is never full

Hi Larry, BTW, there is an open improvement https://issues.apache.org/jira/browse/IGNITE-5003 for the issue you faced. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Incorrect map query built when joining with a subquery with group by statement

Following up on the previous discussion, I have filed an issue regarding the problem : https://issues.apache.org/jira/browse/IGNITE-6865 I have found a workaround this issue by using FROM (select * from Persons) instead of FROM Persons directly, which seems like a bug, because the 2 queries should