Re: Apache Ignite 2.8 release timeline ?

See the wiki for the current status: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8 In summary, the target is mid-January. Regards, Stephen > On 12 Nov 2019, at 00:00, apada...@kent.edu wrote: > >

Re: Ignite.Net Server & client node

As I understood, you store the whole list of 1 employees as a single object: cache[key] = GetAllEmployees(); Instead, try storing every employee object separately: foreach (var employee in GetAllEmployees()) cache.Put(employee.Id, employee) This way you can retrieve individual employees

Re: Ignite.Net Server & client node

Hi Pavel, Scenario is - i am caching list of let's say 1 employee poco class objects with name 'employeeCache'. Now, from this cache, I want to get employee object with id 1500. 1) For this what is fastest & efficient way ? Simple one is get full cache data i.e. 'employeeCache' object and

Re: Ignite.Net Server & client node

Iliya, Thanks. Regards, Sudhir On Monday, November 11, 2019, Ilya Kasnacheev wrote: > Hello! > > Oh! In this case there's not much to do, except maybe use something like > EhCache for local opportunistic caching. > > Regards, > -- > Ilya Kasnacheev > > > пн, 11 нояб. 2019 г. в 10:43, Pavel

Apache Ignite 2.8 release timeline ?

Apache Ignite 2.8 version release time line ? Hi Ignite developers, Do you have any time line for Apache Ignite 2.8 release. I am looking for Version 2.8 for specific enhancement that Ignite team has done : https://issues.apache.org/jira/browse/IGNITE-8571 Baseline auto-adjust feature

Apache Ignite 2.8 release timeline ?

Apache Ignite 2.8 version release time line ? on Nov 11, 2019; 10:38am Hi Ignite developers, Do you have any time line for Apache Ignite 2.8 release. I am looking for Version 2.8 for specific enhancement that Ignite team has done : https://issues.apache.org/jira/browse/IGNITE-8571 Baseline

Re: excessive timeouts and load on NODE_JOINED and NODE_LEFT events

Hi Ilya, Can we restrict PME operations for client nodes explicitly? As far as I know PME does not occur when client nodes are connected. This is a production environment and as you may expect we have many clients joining and removing the grid-nodes under heavy traffic. Any suggestions except

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hi, My first thought is deploying a service [1] (remotely dynamically Ignite.services().deploy() or statically IgniteConfiguration.setServiceConfiguration()) clearing problematic map periodically. [1] https://apacheignite.readme.io/docs/service-grid пн, 11 нояб. 2019 г. в 13:20, mvkarp : > >

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

Hi, Would you have any suggestion on how to implement a last chance workaround for this issue for the server JVM? Ivan Pavlukhin wrote > Hi, > > I suspect a following here. Some node treats itself as a MVCC > coordinator and creates a new RecoveryBallotBox when each client node > leaves. Some

Re: External ignite node is left outside when ignite cluster is restarted

Hi, It's a server node. Can I create a ignite listener to check if the topology size is one which mean it is disconnected and reconnect? On Mon, 11 Nov 2019, 15:21 Ilya Kasnacheev, wrote: > Hello! > > What do you mean by "external node"? Is it a server node or a client node? > > If this is a

Re: excessive timeouts and load on NODE_JOINED and NODE_LEFT events

Hello! When a client node joins or leaves, it will cause a Partition Map Exchange which includes a brief pause. If you have requests with very short timeouts, you can see that some operations will fail. I think there are some client node PME optimizations in the works, in the meantime consider

Re: External ignite node is left outside when ignite cluster is restarted

Hello! What do you mean by "external node"? Is it a server node or a client node? If this is a server node, it will never reconnect to a new cluster. Regards, -- Ilya Kasnacheev пн, 11 нояб. 2019 г. в 11:40, Narsi Reddy Nallamilli < narsi.nallami...@gmail.com>: > I have an ignite cluster

External ignite node is left outside when ignite cluster is restarted

I have an ignite cluster with 2 nodes and another external 1 nodes connected to the ignite cluster . Now if the ignite cluster with 2 nodes restart then the external 1 nodes is left out of cluster. I am interested in finding some way the external 1 node rejoin the restarted cluster nodes. Please

excessive timeouts and load on NODE_JOINED and NODE_LEFT events

Hi igniters, Everytime a client node connects or disconnects from the grid we get exessive number of timeouts and huge load on grid nodes. Current grid-node metrics are the followings; Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=cbdf5b45, uptime=40 days,

Re: Ignite.Net Server & client node

Hello! Oh! In this case there's not much to do, except maybe use something like EhCache for local opportunistic caching. Regards, -- Ilya Kasnacheev пн, 11 нояб. 2019 г. в 10:43, Pavel Tupitsyn : > Ilya, I think thin client was mentioned in the first post - near cache > does not do much for