Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

We're using a cache with CacheMode.REPLICATED. Using 2 nodes, I start each node sequentially and they both get the same number of elements in their caches (as expected so far). Almost immedately, the caches start to drift out sync, all of the elements are simply not getting replicated. There is

Re: Using Apache Ingnite as RDBMS in memory Cache

This depends on the type of queries! In any case: before you go in-Memory optimize your current data model and exploit your current technology. I have seen in the past often purely designed data model that do not leverage the underlying technology well. > On 16 Jun 2016, at 23:20, Andrés

Re: Pre Hook before actual Ignite commit

Yes, this should be enough. Let us know if you have more questions on this. — Denis > On Jun 17, 2016, at 5:52 AM, amitpa wrote: > > Yes you understood it fine. > > First of all our read-write through is setup correctly. > > So looking into the example you provided, I

Re: Pre Hook before actual Ignite commit

Yes you understood it fine. First of all our read-write through is setup correctly. So looking into the example you provided, I think only this line to my existing configs should do the trick:- cacheCfg.setCacheStoreSessionListenerFactories(new Factory() { @Override public

Re: Ignite with Cassandra and SSL

Igor R., Alexey K. or Val, Is SSL presently supported for Cassandra cache store? — Denis > On Jun 13, 2016, at 11:34 AM, ChickyDutt wrote: > > Good morning > > Could you please help me understand how to establish persistence to > Cassandrea via SSL? > > What else

Re: Production outage - Join process time out

Hi, Please properly subscribe to the user list (this way we will not have to manually approve your emails) if you want to get answers from the community earlier. All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. Is there any

Re: performance issues

Hi, In a single server mode (embedded) there is no I/O (networking) at all. All the requests are executed locally. When you use the client node you’ll have I/O delays. The performance here can depend on several factors: - latency and throughput of your network; - CPU saturation; So take a look

Re: Ignite - Spark integration

Hi, As I see you already got the answer in the following discussion How deploy Ignite workers in a Spark cluster Let’s keep discussing in one thread. — Denis > On Jun 13, 2016, at 12:40

Re: Issue with automatic persistence

Hi, Do you see the working below on any of the nodes? Failed to register marshalled class for more than 10 times in a row Actually it’s difficult to say what is the exact reason of the issue. Can you upgrade to the latest Ignite version to see if the issue is still reproducible? — Denis > On

Re: Pre Hook before actual Ignite commit

Hi, If I understand your use case properly you want all the updates that happen inside of an Ignite transaction to happen inside of a single DB transaction on remote nodes. Is it so? If yes then you CacheStoreSessionListener interface [1] is what you’re looking for. In particular since you’re

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Hi, If you want to initialize CassandraCacheStoreFactory programmatically you need initialize the following on Java side as well: - CassandraCacheStoreFactory.setDataSource(DataSource dataSrc) - CassandraCacheStoreFactory.setPersistenceSettings(KeyValuePersistenceSettings settings) DataSource

Re: Using Apache Ingnite as RDBMS in memory Cache

Hi, To achieve the performance boost you need to use Apache Ignite SQL engine [1]. However all the data has to be located in caches (RAM). SQL engine doesn’t work against RDBMS. So you need to preload data into caches from RDBMS using one of existed approaches [2]. After that you can start

Re: transaction not timing out

Hi Binti, Could you share with me a snippet of this code and cache configuration for validation? Do you set timeout before any operation inside of the transaction is executed? Please try to use the following method setting the timeout - IgniteTransaction.txStart(TransactionConcurrency

Re: Using Apache Ingnite as RDBMS in memory Cache

Hello, I'm new with Apache Ignite, I'd like to know how can I use Apache Ignite cache to bust up RDBMS queries. I saw it in apache conn that is possible perform querys against RDBMS allowing to speed up it's execution Regards. -- Ing. Ivaldi Andres

performance issues

Hi, I am trying to run the yardstick ignite benchmark test on my local VM having 8 Cores and 16GB RAM. I could see that the performance of Optimistic PUT/GET is way low for a client-server mode than what I see when running within one single server (embedded mode). Also the performance degrades

CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Hi, I'm trying to use Cassandra as persistent store for my cache. I'm following example given online but trying to configure CassandraCacheStoreFactory using java instead of xml. I know there's limitation because of serialization but just wanted to try it out first. I keep getting exception

Re: schema import example ClassNotFoundException: org.apache.ignite.schema.H2DataSourceFactory

Hi I suppose you try to start Ignite with generated pojos? If yes attach the code responsible for running the output. 2016-06-14 15:36 GMT+03:00 xoraxax : > I am trying to run schema import example and it throws me this exception on > remote nodes. > peerClassLoadingEnabled is

Re: Ignite performance improvements

Optimistic should show better performance than pessimistic transactions. The main point about OPTIMISTIC READ_COMMITTED is that during a commit it’s not checked if an entry value has been modified since the first read or write access and an optimistic exception is never raised. However

Re: Pre Hook before actual Ignite commit

Something like a Spring TransactionSynchornizationmanager. But using that will not work, because it workds for the current node, and Ignite can choose to do the final commit in other JVMs. My problem is that I have 4 caches with Write Through. They use Spring Transactions to do JDBC

Re: Ignite performance improvements

Does OPTIMISTIC Serializable give better performance? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5684.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite performance improvements

> Lastly my CPU load is less than 50% when the transactions takes place (4000 > TPS). I would add that most likely I/O is a reason of why CPU is not fully utilized. You have two nodes both of the communicating over shared memory (I/O) and CPU will stall for some period of time. If you run your

Re: Ignite performance improvements

Hello, Growth loading CPU to 90% may caused by work of GC. For determine this you can get log and analyze log of GC [1]. Also you can use Unix utility for detection causes like dstat or top. In further 50% CPU usage is maybe normal for your case (transaction OPTIMISTIC, READ _COMMITED). You can

Re: transaction not timing out

Thanks Denis, did not realize I was creating a new cache with that name with default settings. However, this was a test case, I fixed it and I can it timing out. The real issue we see in our UAT enivornment is as follows. All caches are defined as TRANSACTIONAL in the config file. But we see one

Pre Hook before actual Ignite commit

Hi, I want to initiate certain things, before the Ignite Transactions commits. Is there any hook which I could use to do that, which will be called in the node which has bene chosen as the Ignite Primary? -- View this message in context:

Issue with automatic persistence

Hi, We are using ignite cache with automatic persistence feature for storing the objects in cache. We have objects used as key and value for this cache. Sometimes when we start our application we get the following error while we try to push any value in this cache. It is very random behaviour.

Re: Change rest-http Java to JSON null transformation logic

Den, that was my main reason "consistency". Strings in java can be "null" and can be empty. But after serialization we lost this info. As for compatibility - I'm afraid it is impossible to fix. Only to change user code. On Thu, Jun 16, 2016 at 4:51 PM, Denis Magda wrote: >

Re: Change rest-http Java to JSON null transformation logic

Pavel, we cannot omit them. Because if JSON will be transformed back to Java and some java field has not null default value that will lead to not correct de-serialization in this case. On Thu, Jun 16, 2016 at 4:54 PM, Pavel Tupitsyn wrote: > Why do we even write null

Re: Ignite - Logging - Using Logback and setting logging level

Actually, you even don't need these two lines and jul-to-slf4j library. Ignite will work well with rest. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Logging-Using-Logback-and-setting-logging-level-tp5652p5674.html Sent from the Apache Ignite Users

Re: Change rest-http Java to JSON null transformation logic

Pavel, in this case object will be serialized like : {"a": "null"} compare with {"a": null} On Thu, Jun 16, 2016 at 4:49 PM, Pavel Tupitsyn wrote: > Hi, > > What if there is an actual string with "null" value? > > Pavel. > > On Thu, Jun 16, 2016 at 12:44 PM, Vladislav

Re: Change rest-http Java to JSON null transformation logic

Hi, What if there is an actual string with "null" value? Pavel. On Thu, Jun 16, 2016 at 12:44 PM, Vladislav Pyatkov wrote: > Hello, > > Why do you want this, if you can save full compatibility using custom > serializer for null value

Re: Change rest-http Java to JSON null transformation logic

Hello, Why do you want this, if you can save full compatibility using custom serializer for null value (ObjectMapper#setSerializerProvider)? On Thu, Jun 16, 2016 at 12:15 PM, Alexey Kuznetsov wrote: > Hi All! > > I'm working on migrating from outdated json-lib to

Re: transaction not timing out

Hi Binti, There is an issue in your code. The cache that is used for transaction operations is not transaction, it’s atomic. The following code below will properly create the transaction cache for you and you will get the timeout exception this.ignite =

Re: How do I know the cache rebalance is finished?

Hi Andrew, > Cache API's put method can not satisfy the performance and DataStreamer can > not keep messages ordered, So I chose the IgniteMessaging(someone of > igniters recommended to me a couple of months ago). You should keep in mind that IgniteMessaging.sendOrdered is not synchronized

Re: Asynchronous cache batch write data can not be asynchronous execution

Hi, Thank you very much! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asynchronous-cache-batch-write-data-can-not-be-asynchronous-execution-tp5638p5664.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.