Transaction Speed

Hello, what are some options to increase the transaction speed? (CacheAtomicityMode = TRANSACTIONAL). Thanks, Ricky - -- Ricky -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Persistence on Kubernetes.

I wouldn’t say that distributed and relational disk-based databases are not suited for Kubernetes. For instance, Cassandra [1] and MongoDB [2] are supported via the mentioned StatefulSets. Current Ignite integration doesn’t tap into the StatefulSets. Once it’s done Ignite persistence can be

Re: We want to configure near cache on client so that we can handle high TPS items and avoid network call to server

1. But we want to configure different eviction policy for near cache. According to documentation, setNearEvictionPolicy(CacheEvictionPolicy) - Eviction policy for the near cache. nearConf.setNearEvictionPolicy(new LruEvictionPolicy<>(1000)); But looks like the below configuration is not working

Schema vs CacheName

Hello, I am a bit confused about schemas and cache names. In some cases they seem synonymous, on others the appear different. So far I have defined everything in XML configuration. To execute a query, I get the cache [getOrCreateCache()], and then execute the query statement. When the

Re: Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Denis, I can confirm the same configuration works in 2.0. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-1-0-Thread-deadlock-on-DefaultSingletonBeanRegistry-getSingleton-tp16481p16521.html Sent from the Apache Ignite Users mailing list archive at

Re: Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Alex, Does it mean you could reproduce the issue in 2.1 and confirm it doesn’t exist in 2.0? I’m curious what happened in 2.1 release so that we got this bug. — Denis > On Aug 29, 2017, at 1:01 PM, afedotov wrote: > > Hi, > > Looks like with IgniteSpringBean

Re: Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Hi, Looks like with IgniteSpringBean and a @SpringResource configured for a CacheStore a deadlock occurs, since IgniteSpringBean singleton creation takes a Spring internal lock and after that tries to start a cache with a CacheStore in a separate thread in a synchronous way, it sees that a

Re: Retrieving multiple keys with filtering

Ah, yes! Thank you, Semyon! According to invokeAll() javadocs "No mappings will be returned for EntryProcessors that return a null value for a key." I should read JCache javadocs more carefully next time. :) Still, the processor is invoked while a monitor is held on the cache entry being

Re: ignite cron scheduling in cluster

Hi, There is no such functionality out of the box right now, but you can implement something like this with your own. For example, run broadcast on all nodes to scheduleLocal jobs which will check after starting that only one of them will run and all other just will finish. But in this case, you

Re: We want to configure near cache on client so that we can handle high TPS items and avoid network call to server

Hi, 1. It's mostly OK, but expiry policy should be set on the main cache and it will be inherited by the near cache Please refer to this documentation section 2. It's not possible out of the box, but you could do some

Re: Limiting the size of Persistent Store and clearing data on restart

Hi, 1) There is no possibility to limit Persistent Store size right now, but you always can use separate disk volume with size 300GB for your case to use it for Persistent Store. 2) Well it's not usual to use case, but after stopping node you can clear data from work folder or just invoke

Re: GC stalling all the activity

Hi Dmitry, I have *not* explicitly set setOnheapEnabled to true which means it gets the default value. At the same time, I have *not *mentioned any DirectMemorySize related jvm parameter. The only parameters mentioned are Xms and Xmx as 1G. I will parse the heap dump tomorrow and give you the

ignite cron scheduling in cluster

Hello All, Apache ignite was very useful in our product, but have a query regarding schedulers cron as given below: We noticed that we can provide cron expression for a job to run only on local node (i mean with the cron the job will run recurrently in the local node only). Is there anyway for

Re: Ignite Persistence on Kubernetes.

Hello takumi, There's a walk-through on deployment in Kubernetes: https://apacheignite.readme.io/docs/kubernetes-deployment You would probably want to use StatefulSets for persistence-enabled Ignite: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/ "Manage the deployment

Re: GC stalling all the activity

Hi, What is the size of your objects? Have you set CacheConfiguration.setOnheapEnabled() to true? Can you get heap dump and check out biggest consumers and their nearest roots? Normally all entries will go to off-heap, if it doesn't fit off-heap memory it starts swapping to disk. But loading may

Re: Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Igor, Could you share a test to reproduce the issue? — Denis > On Aug 29, 2017, at 3:59 AM, igor.tanackovic > wrote: > > Upgraded Ignite from 2.0.0 to 2.1.0 and ran into a thread deadlock on Ignite > startup. I noticed the deadlock once I added CacheStore into a

Re: Configure Apache-Ignite as Out-Proc instead of in-Proc

Hi, Yes, just start a node from a command line tool: https://apacheignite.readme.io/docs/getting-started#start-from-command-line — Denis > On Aug 28, 2017, at 11:19 PM, Shuvendu Das wrote: > > Hi , > > Is there any configuration to make Apache-Ignite to run as

Re: How to configure off heap and "native" distributed persistence

Thanks, got it working. This helped a lot too: https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples/persistentstore -- View this message in context:

Limiting the size of Persistent Store and clearing data on restart

Hi All, 1) Like the conventional configuration of https://apacheignite.readme.io/docs/memory-configuration#section-memory-policies where in we could limit the size of the memory, how do we define a configuration which can limit the size of Persistent Store so that say out of a 500GB HDisk, I

Re: Ignite 2.0 transaction timeout not holding up

Hi, This timeout is for the whole transaction, but when for the transaction you usually need to take locks on different nodes. So, when the transaction was succeeded in acquiring locks on one node, it sends remaining timeout o next node, to acquire locks on it. For example, when you see

Re: How to configure off heap and "native" distributed persistence

Yes, Ignite support native persistence, documentation for this was mentioned in your first message Simple configuration for enabling it: Evgenii 2017-08-29 18:16 GMT+03:00 matt : > Maybe I'm not understanding this correctly but doesn't Ignite support a >

Re: How to configure off heap and "native" distributed persistence

Maybe I'm not understanding this correctly but doesn't Ignite support a "native" persistence solution, where data is written to disk? If so, where can I learn more about configuring this behavior? I'm expecting that once enabled, a restart of the node would have the cache populated from what was

Re: SQL query is slow

It is possible returned dataset is too large and cause high network pressure that results in large query execution time. There is no recommendation for grid nodes count. Simple SQL queries can work slower on large grid as most of time is spent in inter-node communication. Heavy SQL queries may

Re: Error during activation of cluster

Thanks Evgenii Please allow me sometime, I will post that information. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-during-activation-of-cluster-tp16478p16502.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

GC stalling all the activity

Hi all, I have started 2 Ignite Data Grid servers with initial and maximum heap of 1G with PersistentStore configured. Clients come in and persist the data to these servers concurrently. Irrespective of the size of the data, I thought when it is not able to fit within 1 gb, it will get persisted.

Re: Anaemic Domain Model

Hi Narayana, Can you describe the difficulties that you have with storing rich model classes in Ignite? Anaemic domain model is controversial, opinions range from "good practice" to "anti-pattern". Ignite does not force you into any specific approach, IBinarizable and IBinarySerializer

Re: Error during activation of cluster

Hi, To investigate this issue we need some additional information from your nodes: 1. Persistence config from all nodes. 2. Catalog structure from C:\Data\IPD\WAL\ and from pathes from other nodes. 3. Checkpoint files from work/db/{NODE_ID}/cp - they are have a small size. Evgenii -- View

Re: 1 processing node, n partition nodes

Ah that makes sense! I'll try that out. Thanks, - Matt -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/1-processing-node-n-partition-nodes-tp16485p16498.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How to configure off heap and "native" distributed persistence

Ok thank you, I was looking at CacheConfiguration and not IgniteConfiguration. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-configure-off-heap-and-native-distributed-persistence-tp16488p16497.html Sent from the Apache Ignite Users mailing list archive

Anaemic Domain Model

Hi all, I am using Apache Ignite (.NET) in a web application. My domain model classes are directly stored in Ignite cache, and I have persistence in SQL Server. I have DTOs to SQL Server, but none to Ignite. I can see that I am following an anaemic domain model due to several restrictions. I

Re: Failed to wait for partition map exchange

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. Which Java versions do you use in both cases? In eclipse and

Re: How to configure off heap and "native" distributed persistence

Are you sure that you try to set it for IgniteConfiguration and not for CacheConfiguration? Evgenii 2017-08-29 16:36 GMT+03:00 matt : > OK thanks Evgenii. For the persistence, I'm trying the Java example here: >

Re: 1 processing node, n partition nodes

Hi, What do you mean by 1 node that processing data? If you want to store data on several nodes and run some compute jobs that use data from these caches only on one node, then I could say that it a bad idea - it will lead to a lot of data moving between nodes. It's better to use affinityCall to

Re: How to configure off heap and "native" distributed persistence

OK thanks Evgenii. For the persistence, I'm trying the Java example here: https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store but the setPersistentStoreConfiguration method does not exist on CacheConfiguration. I'm on Ignite 2.1.0 - what am I doing wrong? Thanks, - Matt --

Re: How to configure off heap and "native" distributed persistence

Hi, By default, since version 2.0 Ignite use Off heap memory, so you don't need to configure it explicitly. No, you don't need additional dependencies to use persistent store Evgenii 2017-08-29 16:05 GMT+03:00 matt : > I found doc references via Google search to >

Re: Retrieving multiple keys with filtering

Hi, If EntryProcessor returns null then null is not added in the result map. But I agree that using invokeAll() will have a lot of unnecessary overhead. Perhaps we need add new getAll method on API, otherwise best alternative is use custom ComputeJob or affinityCall. Thanks, Semyon On Tue, Aug

Re: History, multiple source systems, Data Vault using Ignite...

Hi, Yes, it's possible to implement storage for previous values in Ignite. For example, you can use listener of ContinuousQuery with @IgniteAsyncCallback for updating values in your cache. When value updated, you can put previous value(which will be available in this event listener) in another

How to configure off heap and "native" distributed persistence

I found doc references via Google search to CacheConfiguration.setMemoryMode() but 2.1.0 does not seem to have this method. How do I configure off heap mode? And for the distributed persistence support: https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store - Do I need an

Re: Configure Apache-Ignite as Out-Proc instead of in-Proc

Hi, If by *Out-Proc* you mean running Ignite as a standalone process, not as a part of an existing application, then yes, it's possible. You could run an ignite node from the shell using the startup scripts located in $IGNITE_HOME/*bin* directory. As well you could create a separate app, the

1 processing node, n partition nodes

Hi, Can someone recommend what CacheConfiguration settings would be ideal for a cluster that has 1 primary node processing data, while other nodes are there to host partitions for the purpose of reducing the primary node memory requirements? How can I control the size of the local cache per node,

Re: Reusing CacheStores connections?

Hi, Please consider using some kind of pooled DataSource instead of using simple DriverManager.getConnection for obtaining a connection. Kind regards, Alex. On Tue, Aug 29, 2017 at 5:57 AM, Matt-2 [via Apache Ignite Users] < ml+s70518n16468...@n6.nabble.com> wrote: > Hi, > > Following the

Re: NullPointerException at unwrapBinariesIfNeeded(GridCacheContext.java:1719)

Hi, Looks like there was a race. Try to upgrade to ignite-2.1 as its includes a few object serialization fixes. On Mon, Aug 28, 2017 at 8:40 PM, zbyszek wrote: > Dear All, > > I was wondering if this is a know issue (I am using 2.0) and if I could > prevent it somehow. > I

Re: Possible starvation in striped pool. message

I did try your suggestion. My code: some = ignite.compute().affinityCall(CACHE_NAME,1, () -> cacheBinary.get(1).field("some")); And i get ClassNotFoundException for the object class which is put into cache. peerClassLoadingEnabled is set to true. -- View this message in context:

Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Upgraded Ignite from 2.0.0 to 2.1.0 and ran into a thread deadlock on Ignite startup. I noticed the deadlock once I added CacheStore into a cache configuration which has Spring Data repository injected using @SpringResource. Ignite hangs during startup with one of executor threads blocked.

Re: Failed to run reduce query locally

Thanks, tried and it seem this issue has been fixed. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-run-reduce-query-locally-tp16403p16480.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Server and Client Configuration for different use cases

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. You can find a lot of example for .Net here

Error during activation of cluster

Hi team, I am using using PersistentStore configuration for Apache Ignite. I started 2 servers 1 on PC1(local) and other one on a PC2(local) connected to the same network. Both the servers got started and the topology also stated that GridDiscoveryManager - Topology snapshot [ver=2, servers=2,

Re: Ignite 2.0 server node shutdown

Hi Amit, No, Ignite node should not be stopped automatically because of a period of inactivity. The one of possible reason for automatic shutdown may be a segmentation (node was segmented out of the cluster). Usually this happens because of long GC or temporary network problems, when node

Re: SQL query is slow

Hi, You can try to 1. add more nodes to reduce data set on each node. 2. use query parallelizm [1]. 3. add a indexed field to be used in WHERE clause instead of function. [1] https://apacheignite.readme.io/docs/sql-performance-and-debugging#query-parallelism On Tue, Aug 29, 2017 at 12:09 PM,

SQL query is slow

We have a cache with ~3million entries We execute the following query: select count(_key) from IgniteProduct as product where POSITION ('Z',manufacturerCode)>0 The query takes about 7s though the index is hit. Query execution is too long [time=7103 ms, sql='SELECT COUNT(PRODUCT__Z0._KEY) __C0_0

Configure Apache-Ignite as Out-Proc instead of in-Proc

Hi , Is there any configuration to make Apache-Ignite to run as Out-Proc instead of in-Proc thanks Shuvendu