Re: SQLQuery with simple Join return no results

Yes, this one of the ways. Denis On Friday, September 1, 2017, matt wrote: > OK thanks for that. So does that then mean that the key type (K) for my > Cache > needs to be AffinityKey ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Quick questions on Evictions

Hi, I have been reading through Ignite doc and I still have these questions. I appreciate your answer. Assume my Ignite native persistence is *not *enabled: 1. if on-heap cache is also not enabled, then there are no entry-based evictions, right? 2. if on-heap cache is now enabled, does

Re: SQLQuery with simple Join return no results

OK thanks for that. So does that then mean that the key type (K) for my Cache needs to be AffinityKey ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: SQLQuery with simple Join return no results

If you use Strings as the keys you won’t get affinity collocation set up properly and distributed joins will return an incomplete result. One of the keys have to comprise a “parent” class key that will be an affinity key. Look at the example here: https://apacheignite.readme.io/docs/affinity-col

RE: SQLQuery with simple Join return no results

Hi Matt, are the objects to join collocated, ie. do they have the same affinity key? If yes, it should work (it worked for me). If no, you need to enable distributed joins for the query. See the middle line. SqlFieldsQuery qry = new SqlFieldsQuery( stmt); qry.setDistribu

Re: Memory is not going down after cache.clean()

Thanks Dmitry, Is it possible to limit the maximum memory size, if maxSize is configured with memory policies for a cache without persistence ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory is not going down after cache.clean()

Yes, maxSize parameter always limits amount of space available for an Ignite node in RAM (doesn’t matter whether you use persistence or not). https://apacheignite.readme.io/docs/memory-configuration — Denis > On Sep 1, 2017, at 2:19 PM

Re: Memory is not going down after cache.clean()

Thanks Dmitry, Is it possible to limit the maximum memory size, if maxSize is configured with memory policies for a cache without persistence ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

SQLQuery with simple Join return no results

I have 2 caches defined, both with String keys, and classes that make use of the Ignite annotations for indexes and affinity. I've got 3 different nodes running, and the code I'm using to populate the cache w/test data works, and I can see each node is updated with its share of the data. My index t

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Last time I tried, which was early 2017, cache.getEntry() would pull it from Cassandra (or whichever database is backing the cache) for me, while cache.get() won't. I then found somewhere, in the docs or on the board, that it's to be expected. Can someone confirm? I was most interested in SQL, whic

Re: Ignite 2.0 out of memory

Thanks for the quick response. how many nodes you have on the one machine? we have single ignite node on the machine. How many visor clients on it machine? we mostly monitor ignite using ignitevisor, and it might have happened the visor client did not shut down correctly. I think, it could be an

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

I would recommend changing ignite .getOrCreateCache(new CacheConfiguration( Application.TEST_CACHE_NAME))) to ignite .cache(Application.TEST_CACHE_NAME) just to check if you really accessing the same cache that was creating from your xml file and not creating a new one with empt

Re: Ignite 2.0 out of memory

This error is not about heap memory, it indicates that you started more threads within one process that it's allowed by OS. On Linux you can play with ulimit to overcome the issue. Also, how many nodes you have on the one machine? How many visor clients on it machine? Could you share logs from nod

Re: Task management - MapReduce & ForkJoin performance penalty

Hi, I've added Thread.sleep(200) to Jobs to simulate a small load. Here is what I've got: 1node: 1 Task 2000 Jobs ~25 sec 2nodes(on the same machine): 1 Task 2000 Jobs ~13 sec What I want to say here - this overhead will be not noticeable on real Jobs. What about some configuration changes - yo

Ignite 2.0 out of memory

Hello igniters, I see the following warning in the log - [17:23:29,070][WARN ][main][TcpCommunicationSpi] Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.

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

Sorry, I didn't know that. I found a bunch of matches by "swapEnabled" keyword on master branch in the project, mostly in benchmarks configurations. These properties should probably be removed not to confuse readers. пт, 1 сент. 2017 г. в 19:23, Dmitriy Setrakyan : > On Fri, Sep 1, 2017 at 1:41 P

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

On Tue, Aug 29, 2017 at 7:00 PM, userx wrote: > 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

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

On Fri, Sep 1, 2017 at 1:41 PM, Denis Mekhanikov wrote: > Regarding your second question: looks like you don't actually need > persistence. Its purpose is the opposite: to save cache data between > restarts. > If you use persistence to store more data than RAM available, then you can > enable swa

Re: Cache Events for a specific cache.

Hi Chris, Your listener receives CacheEvent, which contains cache name, key and value. You may just check cache name and react accordingly [1] or use ContinuousQuery as you suggested. [1] https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/Cache

Re: fetching all the tasks already scheduled and to know the status of the task

Hi, You could use *ignite*.compute().activeTaskFutures() to get the map of all the active tasks started from the *ignite* node. Kind regards, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory is not going down after cache.clean()

Hi, Ignite can only increase memory consumption, there are no ways to reduce it. Practically it's not needed, because it's enough just to set desired memory size, and if persistence enabled - swap data to disk, when this limit was hit. Thanks! -Dmitry. -- Sent from: http://apache-ignite-users.

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

FYI, my update wasn't that my problem was solved, but that the website got rid of the work that I did to post the code. Please take a look at the code that I've posted yesterday because I'm still having the issue. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Configuring path of binary_meta, db directories etc

Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

Regarding your second question: looks like you don't actually need persistence. Its purpose is the opposite: to save cache data between restarts. If you use persistence to store more data than RAM available, then you can enable swap space: https://apacheignite.readme.io/v1.9/docs/off-heap-memory#se

Re: IgniteCache.localEntries(CachePeekMode... peekModes) result

Hi, > when we call cache.*localEntires *and we get the Iterable https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html> ,V

Re: hashcode() collisions for data having more than 2 power 32(around 4.3 billion) entries in ignite cache

Hi! Hash code used by Ignite is indeed 32-bit, but it seems to be enough in most use-cases. If you put so many objects into a cache, then collisions will definitely occur, but they will be resolved using 'equals' methods. Collisions happen on much smaller datasets, this is part of normal work of

hashcode() collisions for data having more than 2 power 32(around 4.3 billion) entries in ignite cache

Hi I am using a user-defined java object as a cache key in my ignite cache. Ignite uses the cache key objects overridden hashcode() method during mapping in cache. But hashcode() method returns an int which is 32 bits. Now if my cache has entries more than 2 power 32 which is around 4.3 billion ,

IgniteCache.localEntries(CachePeekMode... peekModes) result

Hello All, I have a question about IgniteCache's *localEntries(CachePeekMode * *... peekModes)* method result. In our case we are using Ignite 2.1.0 We are broadcasting a closure to our ignite nodes to c