Re: Enforcing data to be stored in Heap only

Hi Val, Thanks for the response. The onHeap get performance is better than getting from offHeap especially for our use-cases. We get the data, update and put it back multiple times. With every such request, the deserialization overhead from offHeap adds up. We can't take such an overhead to

Multi Cloud Deployment Issue

Hi, I am trying to setup a multi-cloud cluster of Ignite 2.0 servers and facing severe issues in terms of the response time. I am running Tomcats as Ignite clients hosting my REST service. To narrow down the issue, I tried setting up the cluster in almost all permutation combinations. 1. Two

Re: Multi Cloud Deployment Issue

HI Mikhail, Thanks for the response. I am aware that the data center replication/HA is available in the paid version of Ignite. At this point, I don't have the option to go for it. What I am trying instead is to minimize my risk by distributing the data between different clouds not necessarily

slowClientQueueLimit and messageQueueLimit

Hello Everyone, To manage the slow clients, Ignite provides 'slowClientQueueLimit' configuration on TcpCommunicationSpi. There is another configuration 'messageQueueLimit'. Could you please help me understand the difference between the two and whether - 1. slowClientQueueLimit is configured on

Large value of idleConnectionTimeout in TcpCommunicationSpi

Hello Everyone, One of our cache access pattern is that it is accessed beyond an interval of 30 seconds (which is the default connection timeout). Every time it happens the first call to the cache takes a long time to fetch the results. I am planning to increase the idleConnectionTimeout to a

Enforcing data to be stored in Heap only

Hello Everyone, I am using Ignite 2.0 and want to use heap to cache my data. I have enabled it through the api setOnheapCacheEnabled provided in the CacheConfiguration. Let's say I have a total RAM size of 12 GB. I have set both Xms and Xmx to 8 GB while starting the Ignite server. The reason I

Re: Large value of idleConnectionTimeout in TcpCommunicationSpi

Hi Val, So do you think we can keep a bigger value for idleConnectionTimeout (few hours) without any untoward behavior? Please suggest. Thanks -- View this message in context:

Re: Multi Cloud Deployment Issue

Hi Mikhail, It is critical for us to prove Ignite performance on atleast 2 clouds (not necessarily data center replication) before enterprise wide adoption. Any tips to improve its performance would be appreciated. Thanks -- View this message in context:

Re: Multi Cloud Deployment Issue

Hi Mikhail, It is critical for us to prove Ignite performance on atleast 2 clouds (not necessarily data center replication) before enterprise wide adoption. Any tips to improve its performance would be appreciated. Thanks -- View this message in context:

OOM in Heap though offHeap is available/free

Hi, I am using onHeap along with the default offHeap memory in my Ignite 2.0 server nodes. I am getting out of memory error even though there is enough memory available offHeap. My understanding (based on my earlier posts) is that onHeap is just a cache for offHeap. If that's how it works then

Re: Visor CLI not working (Apache Ignite 2.0.0)

I am running Ignite on Linux. There are 4 VMs where I have set up Ignite. All the VMs have exact same configuration. The details for one of the VM configuration is below - Installation directory - /opt/ignite Command used to run ignite (from /opt/ignite directory) - ./bin/ignite.sh Command

Re: Ignite 2.0 visor issue

I am running Ignite on Linux. There are 4 VMs where I have set up Ignite. All the VMs have exact same configuration. The details for one of the VM configuration is below - Installation directory - /opt/ignite Command used to run ignite (from /opt/ignite directory) - ./bin/ignite.sh Command used

Visor CLI not working (Apache Ignite 2.0.0)

Hi Everyone, I am using Ignite 2.0.0 and trying to launch the visorcmd cli. It shows the 'Connected' message but always outputs 'No caches found' message. The aforementioned cache exists on the cluster though as I can query it through a java client. The commands I use to run Ignite cache and the

Re: Ignite 2.0 visor issue

Hi, I am also facing the same issue with visor on ignite 2.0.0. Could you please let me know what the resolution was at your end. Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p13869.html Sent from the Apache Ignite

RESTART_JVM Segmentation Policy

Hi, I am trying to define the 'RESTART_JVM' network segmentation policy in the configuration xml. Do I need to provide custom segment resolver to handle it or ignite provides the handler to restart the jvm? Also, is the segmentation ignite configuration applicable only to ignite server nodes or

Re: Enforcing data to be stored in Heap only

Hi Val, Would the BinaryObject api improve the performance even if the Key and Value both are user-defined-objects instead of primitives? I have a cluster of 8 ignite server nodes and 8 ignite client nodes (tomcat). My use-case first gets a value for a key to the client node, updates the

Re: RESTART_JVM Segmentation Policy

I am starting the Ignite server nodes through the ignite.sh script only but didn't quite follow if Ignite 2.0 will restart the jvm without a user defined resolver if the segmentation resolver policy is set to 'RESTART_JVM'. Also, does the segmentation policy needs to be defined only on the server

Ignite 2.0 transaction timeout not holding up

Hi, I am using Ignite 2.0 and working with transactions with a 60 seconds timeout. In the logs I see Ignite timeout exceptions with timeout less than 60 seconds in the exception message. The transaction concurrency has been set to PESSIMISTIC and the transaction isolation level is

Ignite 2.0 server node shutdown

Hi, Does a Ignite server node shutdown automatically after a period of inactivity? I am using Ignite 2.0 and found one of my node shutdown with the following logs (below). The last 6 hours of logs just have the node metrics, essentially no application activity. Will the node shutdown under such

Re: Enforcing data to be stored in Heap only

Hi Val, Would the BinaryObject api improve the performance even if the Key and Value both are user-defined-objects instead of primitives? I have a cluster of 8 ignite server nodes and 8 ignite client nodes (tomcat). My use-case first gets a value for a key to the client node, updates the state

Local node failure starts cluster-wide procedure

Hi, Yesterday my Ignite 2.0 cluster went down with segmentation warning in the logs. I have set the segmentation resolver policy as RESTART_JVM and believed that it doesn't work out of the box with Ignite 2.0 even when the node is started through ignite.sh. The logs though revealed that the

Re: Local node failure starts cluster-wide procedure

Hi Val, Thanks for the response. I am trying to figure out the reason why the node was not able to restart when the logs suggest it is attempting. I looked for the 'Restarting JVM...' log in the Ignite code and found it in GridDiscoveryManager$DiscoveryWorker class (pasted below). As per the

Re: Out of memory in client node freezes complete cluster

Hi Ilya, Thanks for the response. I have been following the release notes for every release - 2.1/2.2/2.3. I haven't seen any fixes around this (or similar sounding) issue. Since I am using Ignite is a very critical application, I would like to use a stable version which meets my requirements. I

Re: Deadlock detected while accessing caches

Thanks Andrew for the response. I don't have any getAll/putAll operations but have discovered transaction operations on unsorted keysets on a cache which can cause a deadlock. The deadlock detected message though shows two different caches whereas the unsorted keys are accessed on a single cache

Re: split-brain problem and GridSegmentationProcessor

Hi Luqman, Were you able to work on the custom implementation? If yes, is it available for community use? If no, need your help with a couple of questions - 1. Is the SegmentationResolver needed for server nodes or client nodes? 2. How would the server nodes pick up the implementation on start

Re: Two Ignite Clusters formed after network disturbance

Hi Val, I want to write my own SegmentationResolver for Ignite 2.0. Could you please tell me - 1. If the implementation should be set to IgniteConfiguration only on the client nodes or also on server nodes? 2. If also on the server nodes, then how would the node pick up the implementation on

Deadlock detected while accessing caches

Hi, I have a Ignite 2.0 cluster of 8 servers and 8 clients. It has 6 caches which are transactional and partitioned. I use pessimistic transactions with a timeout of 60 seconds. Under performance testing, I found a deadlock message in the log. I have reviewed the code and there is no cyclic

Re: split-brain problem and GridSegmentationProcessor

Hi Anirudha, we can collaborate on this. Please drop me an email and we can then discuss it. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Out of memory in client node freezes complete cluster

Hi, I am using Ignite 2.0. I have observed that if there is an out of memory error on any Ignite client node, the complete cluster becomes unresponsive. A few details about my caches/operations - 1. Atomicity mode - Transactional 2. Locking - Pessimistic with repeatable read. Is this expected

Re: Ignite Plugin development ...

Hi, I am writing a plugin and have followed the steps mentioned on this conversation but the plugin is not discovered by Ignite node on start up. I have created META-INF/services directories on my Ignite *server* node under the 'libs' directory. I also tried keeping it at the same level as

Re: split-brain problem and GridSegmentationProcessor

Thanks for the details Luqman. I checked another post (link below) and it seems custom SegmentResolver won't be processed. Were you able to make it work? I want to restart the server node if it has disconnected from the cluster so I don't need multiple resolvers. Link -

Re: split-brain problem and GridSegmentationProcessor

So do I need to implement SegmentationResolver as well as GridSegmentationProcessor. Is that correct? I am trying to understand how the GridSegmentationProcessor and SegmentationResolver work in tandem. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unsubscribe Me

Please unsubscribe me from the mailing list. Thanks