Re: Ignite Cluster Disconnects After Idle Time

Updated above post with logs. Text was not showing at first attempt. Thanks, Rami -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Cluster Disconnects After Idle Time

Hi ezhuravlev, I do not have a firewall configured. I was able to reproduce and obtain these logs by enabling the TcpCommunicationSpi logs to DEBUG. One of the nodes seems to be fine when i try to clear the caches: The others seem to fail establishing a Tcp connection: Node 1: Node 2:

Ignite Cluster Disconnects After Idle Time

Hi all, I'm facing hanging issues with my ignite cluster after I leave it idle for 20 mins. The scenario is as follows: I have 3 ignite nodes in one cluster running, each on a container in docker. The cluster is up, nodes have discovered each other and all is stable. I leave the cluster idle f

Re: Cache.destroy() & close() does not delete SwapFile Ignite 2.0

Hi It appears that even when the ignite node shuts down, it does not delete the created cache files. Is there any prebuilt way in ignite to delete these files? Thanks, Ramz -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-destroy-close-does-not-delete-Swap

Re: Swapping to Disk Ignite 2.0

Thank you both for the info :) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Swapping-to-Disk-Ignite-2-0-tp13522p13597.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Swapping to Disk Ignite 2.0

, Ramzinator -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Swapping-to-Disk-Ignite-2-0-tp13522.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache.destroy() & close() does not delete SwapFile Ignite 2.0

Thanks for the tip Alex, I agree it makes sense. As for the file being deleted upon node exit. That doesn't seem to be the case in my test. In any case, I'll make sure to delete the files manually when I'm sure I want to. Thanks Ramzinator -- View this message in context: http:

Cache.destroy() & close() does not delete SwapFile Ignite 2.0

Hi all, I have a Cache that I've configured to use swap space by setting it's policy configuration as such: policy.setSwapFilePath("ignite\\cache"); Yet at the end of my unit tests, when I call cache.close() or cache.destroy(), it does not delete the created file. What can I do to guarantee the

IgniteCache.containsKey does not acquire Transaction lock

Hi all, I've recently upgraded to Ignite 2.0 and noticed that IgniteCache.containsKey no longer acquiring a transaction lock on the passed key. In my experience, it seemed to be the case in ignite 1.8 & 1.9. (Correct me if I'm wrong, I assume a containsKey is considered as a READ cache operation)

Re: Performance issue with Replicated Cache among 7 nodes

Hi Andrey, It turns out that we had increases our failureDetectionTimeout wayyy too much. After setting it to something more sensible, the issue stopped. Thanks for the info, Rami -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-with-Replicated

Performance issue with Replicated Cache among 7 nodes

question is why is the insertion taking so long? Is ignite stuck in a transaction and waiting to timeout? I'd appreciate any help/advice on how to proceed to speed up the insertion. Note that the issue became noticeable when we scaled up the cluster from 3 ignite nodes to 7. Thanks, Ramzi

Re: Ignite Node Discovery IP config

Thank you! This helped a lot. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Node-Discovery-IP-config-tp11957p12013.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cluster Groups with Affinity Behaviour

It's something very specific to my use-case but thank you for clearing it up. I just wanted to make sure that the affinityCall overrides the previous clustering. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-Groups-with-Affinity-Behaviour-tp11952p1199

Re: Ignite Node Discovery IP config

Hi Andrew, I want Node 3 to find both grids. Since Node 3 has both Node 1 and Node 2 ips in its discovery range, my question is why does it only find one of them? Does Ignite node discovery stop upon the first grid discovered? Thanks Ramzinator -- View this message in context: http://apache

Ignite Node Discovery IP config

> However the output is as follows: Node 1: 1 Node 2: 2 Node 3: 2 For some reason, after multiple runs, Node 3 consistently only detects one of Node1 and Node2. Am I missing any configuration to ensure the detection of both nodes by Node 3? Thanks, Ramzinator -- View this message in

Cluster Groups with Affinity Behaviour

oing an affinityCall on the cache, I am sure of the nodes involves in executing the callable? Thanks a lot, Ramzinator -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-Groups-with-Affinity-Behaviour-tp11952.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite RoundRobinLoadBalancingSpi Per Task not distributing tasks.

Hi vkulichenko, The reason is actually a two part problem that I am trying to solve. 1. I want to evenly distribute my ignite computations between the nodes of my cluster as I had noticed that when having 3 nodes and 10 ignite calls, they were being distributed as such 6+2+2=10. Note here I am us

Re: Ignite RoundRobinLoadBalancingSpi Per Task not distributing tasks.

Thanks Anil! It worked great. However, is there a way that Ignite can distribute tasks in a round robin fashion if tasks are called sequentially? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-RoundRobinLoadBalancingSpi-Per-Task-not-distributing-tasks-t

Ignite RoundRobinLoadBalancingSpi Per Task not distributing tasks.

Hi all, I'm trying to use Ignite's RoundRobinLoadBalancingSpi with perTask enabled to guarantee distribution of tasks to my ignite nodes, but it seems that the load balancing is not working as expected. Consider the following test: @Test public void testRR() { Ignite node1 = Ignition.sta

Apache Ignite nodes are not discovering themselves in Docker

Hi all, So I have 2 ignite nodes running in Docker containers. Each container on a separate VM. However the two nodes are not discovering each other at all. I've set the configuration of the ignite to use TcpDiscoveryMulticastIpFinder. This works when the containers are on my 2 VMs on my local ma

Bug with using Map as a cache key in Ignite

Hi GridGain/Ignite guys, I've recently encountered a bug while using Ignite. The scenario is as follows:I have a class *A* that just has a *java.util.Map* field that I am using as an ignite cache key to map to some value. I have 2 instances of the same service: *S1* & *S2* , each running an igni