Re: Ignite DataStreamer Memory Problems

The issue seems to be with the @QueryTextField annotation. Unless Lucene indexes are supposed to be eating up all this memory, in which case it might be worth improving your documentation. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

dumb cache question

What are the restrictions around having two caches in an ignite node that use the same value type? Issues with the sql? Can I have two sql tables of the same class type inside ignite? I thought the answer was no, and saw results verifying that position, but I cannot remember and cannot find

Re: Use case for federated search

Hi, Onur. This gentleman appears to be in Spain. Thank you. ~Jean On Mon, Apr 29, 2019 at 1:54 AM Enrique Medina Montenegro < e.medin...@gmail.com> wrote: > Hi, > > I came across Apache Ignite because I am struggling to find the best > solution to support a federated search from completely

Re: Near cache only on client node

Yes, I found the issue. Actually it was in my Junit. I had accidently added following line in my junit case. This was starting the cache and I was trying to get it using my service call. //final IgniteCache cache = ignite.cache(CacheName.ASSET_GROUP_CACHE.name()); Thanks, Prasad On Mon, Apr

Re: JDBC client disconnected without any exception

Hello! Is it possible that the process was killed by OOM killer? This should be visible in dmesg. Otherwise, we have not heard of such errors. Please share logs of all nodes in cluster, including this client. Regards, -- Ilya Kasnacheev вс, 28 апр. 2019 г. в 10:45, shivakumar : > Hi all, >

Re: Near cache only on client node

Hello! As this error points out, you can't have near cache with same name as already existing regular cache. Regards, -- Ilya Kasnacheev пн, 29 апр. 2019 г. в 13:52, Prasad Bhalerao : > Hi, > > I am getting "*Failed to start near cache* exception" while starting near > cache only on client

Re: Near cache only on client node

Hi, I am getting "*Failed to start near cache* exception" while starting near cache only on client node. Near cache is not configured on server nodes. Cache configuration on server is node is as follows: private CacheConfiguration agCacheCfg() { CacheConfiguration agCacheCfg = new

Re: Diagrams on your website

I think they have drawn it with their hands. On Mon, Apr 29, 2019 at 1:45 PM Johannes Lichtenberger < johannes.lichtenber...@unitedplanet.com> wrote: > Hi, > > for instance the diagrams here: > https://apacheignite.readme.io/docs/memory-architecture > > Thanks and kind regards > > johannes > On

Failed to archive WAL segment

HI all, I have 7 node ignite cluster running on kubernetes platform, each instance is configured with 64GB total RAM(32GB Heap space + 12 GB default data region + remaining 18GB for ignite process), 6 core CPU, 12GB disk mount for WAL + WAL archive, 1 TB separate disk mount for native

Re: Diagrams on your website

Hi, for instance the diagrams here: https://apacheignite.readme.io/docs/memory-architecture Thanks and kind regards johannes On 29.04.19 09:32, Ilya Kasnacheev wrote: Hello! Can you point to any specific diagrams? We have several sites so it's not immediately obvious. Regards, -- Ilya

Re: Diagrams on your website

Hello! Can you point to any specific diagrams? We have several sites so it's not immediately obvious. Regards, -- Ilya Kasnacheev пн, 29 апр. 2019 г. в 10:29, Johannes Lichtenberger < johannes.lichtenber...@unitedplanet.com>: > Hi, > > just wanted to ask with which software you draw these

Diagrams on your website

Hi, just wanted to ask with which software you draw these beautiful diagrams on your website :-) Kind regards Johannes

Re: nodes are restarting when i try to drop a table created with persistence enabled

Hi Shiva, That was designed to prevent global cluster performance degradation or other outages. Have you tried to apply my recommendation of turning of the failure handler for this system threads? - Denis On Sun, Apr 28, 2019 at 10:28 AM shivakumar wrote: > HI Denis, > > is there any

Use case for federated search

Hi, I came across Apache Ignite because I am struggling to find the best solution to support a federated search from completely heterogeneous sources. Let me elaborate a bit more. I have two distinct sources from different providers and I want my users to be able to search in a federated way and