Binary type has different fields error

I just changed a field in a class from a long to a Guid. The class in question is marked [Serializable] and is passed to Ignite compute functions as a part of an argument to the compute function and is not saved to the persistent store. When I run the modified code against an Ignite grid

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Dmitriy, My question regarding cache interceptor availability in .Net is still outstanding. I have working code using a continuous query, but am interested in cache interceptor if this is a better solution. Thanks. Raymond. *From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]

Re: Running Ignite/GridGain in AWS

We are going to go a similar route in AWS (.Net client with .Net standard artifacts inning on Kubernetes). Currently we are looking at whether EBS or EFS is the best option, but the comments here are concerning re Ignite IO bandwidth on those services. What page size are you using? If you

session.removeAttribute is not removing the attribute

What I'm noticing is that session.removeAttribute doesn't really remove the attribute, it only sets the value to null. I'm not sure if this is a setup issue on my end or what. This behavior is causing issues with out existing code. Any input would be helpful. Thanks in advance! dshaw The

Re: Service isn't initialized on cluster re-activation

Hey Denis, I agree with your assessment. I think it's unexpected that the cluster transitions to inactive state prior to services being given a chance to shutdown gracefully. However, to protect the overall cluster health I think we do need some kind of protection against errant services with

client service fail when reconnect,all server nodes stopped then restart

i see some bugs such as https://issues.apache.org/jira/browse/IGNITE-2766 https://github.com/apache/ignite/pull/2627 when i apply the patch, cache can be reused when client reconnect. but

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Hi Raymond, Was this question answered? Sincerely, Dmitriy Pavlov вт, 1 мая 2018 г. в 0:20, Raymond Wilson : > Cross posting to dev list for comment on cache interceptor availability on > Ignite .Net client. > > -Original Message- > From: Raymond Wilson

Unsubscribe

-- Thanks Rajarshi

Re: Service isn't initialized on cluster re-activation

Nick, I agree, that performing heavy work in an exchange thread is generally a pretty bad idea. On the other hand, service cancellation in my opinion should happen, when cluster is in a valid state, when cache operations are still possible. This way service will be able to store useful

Re: Running Ignite/GridGain in AWS

The biggest thing for us using Ignite Persistence on AWS was finding that we needed to use i3 instances for the SSD write performance. Ignite persistences and GP2 was a poor experience. On Tue, May 15, 2018 at 2:43 AM, John Gardner wrote: > We've been running the