Ignite inside OData WebAPI

Hi, I am trying to expose Cache contents as an Odata API. I created the Odata API using ASP.NET WebAPI. Inside the API implementation, I am initializing Ignite in cache mode. Below is the method I am using to retrieve a listing. I have 2 questions. 1. I was not able to use Select option in

Re: Re: Increase Ignite instances can't increase the speed of compute

Hi, Val Thank you very much, I think this is very helpful for me. I will change my compute code, and have a try. Bob From: vkulichenko Date: 2016-09-23 07:00 To: user@ignite.apache.org Subject: Re: Re: Increase Ignite instances can't increase the speed of compute Hi Bob, Most

Re: Logging failing, tried the troubleshoot steps already

I thought the purpose of using log4j was to avoid the steps in that link? The link I included says "you can either add ignite-log4j module to the list of the used jars so that Ignite would use Log4j as a logging subsystem, or alter default Spark classpath as described here." Does "adding it to

Re: Logging failing, tried the troubleshoot steps already

Hi, First of all, you need not only the ignite-log4j jar, but the whole ignite-log4j module with dependencies. Refer to [1] for details. Also as far as I understand, the log4j did replaced the Java logger and you got a different error. Is this right? If so, you should probably just configure

Re: Cannot query on a cache using Cassandra as a persistent store

Hi Guang, Please show the source of the Person class. Does the 'age' field has @QuerySqlField on it? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cannot-query-on-a-cache-using-Cassandra-as-a-persistent-store-tp7870p7893.html Sent from the Apache Ignite

Re: Re: Increase Ignite instances can't increase the speed of compute

Hi Bob, Most likely these are distributed cache operations and since they are all synchronous, you wait for each of them one by one. You can try to batch your updates to improve performance or use data streamer [1]. It would be even better if you used affinity collocation [2] and made sure that

Re: Ignite data nodes without participating in transaction

Hi, DR is not supported out of the box in Ignite. However, GridGain provides this functionality [1] as a part of there paid solution. [1] https://gridgain.readme.io/docs/data-center-replication -Val -- View this message in context:

Re: retrieving values from ignite cache but Rdd don´t show values and long time Java

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. rodrigo thread wrote > I have an application that saves

Re: One failing node stalling the whole cluster

Hi Sparkle, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. sparkle_j wrote > In one of our tests, we noticed

Re: Cluster configuration across data centers

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. newbie wrote > We are evaluating Ignite for caches and have

Logging failing, tried the troubleshoot steps already

I'm trying to implement caching using ignite, and when I start it up (Ignition.start) it throws an error: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler" java.lang.ClassNotFoundException: org.apache.ignite.logger.java.JavaLoggerFileHandler

Re: Cannot recreate cache after cache.destroy()

Hi Alex, You're right. I created a ticket for this issue: https://issues.apache.org/jira/browse/IGNITE-3957 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cannot-recreate-cache-after-cache-destroy-tp7291p7881.html Sent from the Apache Ignite Users

Affinity and Topology versions

Affinity in the cluster is coupled to the topology. Any affinity based processing requires a stable topology. Does Ignite guarantee that all nodes are executing a transaction on the same affinity version? Please correct me if I'm wrong but based on my observation in Race condition with

Re: Out of order updates for CacheEntryListeners and multi-cache transactions

Interestingly, setting cache key affinity appears to resolve the issue, however is there any way to avoid this for cases where there isn't a common cache key on every item, such as foreign keys? e.g. -- View this message in context:

Re: Ignite LINQ Help

That worked. Thanks Pavel. On Thu, Sep 22, 2016 at 2:57 AM, Pavel Tupitsyn wrote: > Hi, > > Your class is serialized with .NET BinaryFormatter, that's why SQL and > LINQ does not work [1]. > > To fix this, remove [Serializable] attribute and register the class in >

Re: Out of order updates for CacheEntryListeners and multi-cache transactions

I've added a code example to github https://github.com/rossdanderson/IgniteOutOfOrderUpdate I appreciate any help here as it basically means there's no way to guarantee read-after-write consistency for events triggered off of a transaction involving multiple caches, even if they access the data

Re: Ignite LINQ Help

Hi, Your class is serialized with .NET BinaryFormatter, that's why SQL and LINQ does not work [1]. To fix this, remove [Serializable] attribute and register the class in BinaryConfiguration: var cfg = new IgniteConfiguration { BinaryConfiguration = new BinaryConfiguration(typeof(MyModel) };