Re: Ignite web console and we agent are running not able to see clusters

Hi, gkiran292! Did you managed to start web agent and connect cluster to Web console? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Question on On-Heap Caching

With Ignite 2+, I have found that the on-heap option makes only modest improvements to performance in most cases. Likewise for copyOnRead=false, which works in conjunction with on-heap. These options work best in the case where you have a small number of cache entries that are read many times. In b

Cache Mode = LOCAL throwing exception while initialisation

Hi, I am trying to create an Ignite cache with cacheMode="LOCAL" and on initialisation it is throwing NPE. localCache XML http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/s

Re: ComputeGrid API in C++

Yes, this will do. Best Regards, Igor On Fri, Oct 27, 2017 at 5:49 PM, asingh wrote: > Ok, so, i first need to wrap ignite within an application that will > register > my user functions and start ignite. > I launch that application on every machine that I have. > Then, I can launch another call

Re: Cache Mode = LOCAL throwing exception while initialisation

Hi Ankit, It is a known bug. Here is a ticket for it IGNITE-6794 [1]. A s a workaround you can set empty MemoryConfiguration on client. [1] https://issues.apache.org/jira/browse/IGNITE-6794 On Thu, Nov 9, 2017 at 2:46 PM, Ankit Singhai wrote: > Hi, > I am trying to create an Ignite cache with

Re: Ignite Nodes not connecting to cluster in docker swam mode

Hi, How many nodes you have? For large grids, there is a recommendation to prestart one node and then start others. Would you please share grid configuration and thread dumps from stucked nodes? On Thu, Nov 2, 2017 at 11:52 AM, rishi007bansod wrote: > Hi, > Initially I was trying with auto

Re: Renentrant Lock & deadlock

Hi, ignite.reentrantLock() creates a cache for datastructures dynamically if is not exists yet. So, both it is same issue. On Tue, Oct 31, 2017 at 7:15 PM, rajivgandhi wrote: > That one was with ignite.getOrCreate > This one is with ignite.reentractLock. > > Are the both due to the same defect?

Re: Deadlock detected while accessing caches

Hi dark, It is known issue. The only workaround here is to presort keys before getAll \ putAll. On Fri, Nov 3, 2017 at 10:05 PM, dark wrote: > I also experienced a deadlock while attempting putAll using a HashMap. > I used AtomicityMode as ATOMIC. > If you are like me, the following process mig

Re: Deadlock detected while accessing caches

Hi Amit, Transactions on unsorted keysets also can cause a deadlock. However, unlikely to getAll on Atimoc cache, Ignite should detect deadlock in transactions. On Thu, Nov 9, 2017 at 3:31 PM, Andrey Mashenkov wrote: > Hi dark, > > It is known issue. The only workaround here is to presort keys

Failed to parse query - Table not found

Hi, I am testing the Ignite native persistence and Spring. I started from the SpringDataExample and change it. I created an XML configuration that is analogous to the Java configuration that can be found at the SpringAppCfg class. I attach the XML configuration for your reference. I start the Ex

ΑΠ: Failed to parse query - Table not found

Hi, I found the issue. I have added this to the XML configuration: java.lang.Long org.apache.ignite.examples.model.Person And it worked! Thank you

Re: Ignite/Cassandra failing to use supplied value for where clause

I can't reproduce the issue. Is it possible you try to get value for key with 'null' id field? On Fri, Nov 3, 2017 at 5:28 AM, Kenan Dalley wrote: > Hi Andrey, > > I tried taking pieces from your example and I still couldn't make it work. > First, I removed the annotations out of the POJOs and p

RE: Node failed to startup due to deadlock

Hi Naresh, Unfortunately I don’t see any attachment, please send them again. Can you clarify your node startup activity. 1) How do you lock the caches? IgniteCache.lock() or IgniteCache.lockAll() locks only a one or batch of cache entries, not the whole Cache. 2) Do you really need some locks if

Re: Out of memory in client node freezes complete cluster

Hello! I would recommend using 2.2 or 2.3 and not 2.0. Having said that, it makes sense to avoid OOM because in many places behavior is undefined once you hit OOM. It should not be hard to avoid. It should not cause cluster to hang, but without logs from server nodes it's hard to understand what

Re: Ignite/Cassandra failing to use supplied value for where clause

I don't see how because this is what's in the table. And the code specifically sets the "myId" to a value before it runs. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Re: When client node query a cache with JDBC storage, report miss the dataSourceBean

Hello Aaron! You can use thin JDBC driver for query only without the need to instantiate cacheStoreFactory on client. Regards, -- Ilya Kasnacheev 2017-11-09 4:34 GMT+03:00 aa...@tophold.com : > Got it thanks Ilya! > > So if we try to totally isolate the client from server, may need start a >

Re: Benchmark results questions

Hi Ray, I've finally got results of query benchmarks: 4s1c 80725.80 80725.80 4s2c 78797.90 157595.80 4s4c 54029.70 216118.80 8s1c 64185.60 64185.60 8s2c 61058.10 122116.20 8s4c 34792.70 139170.80 First column - cluster configuration (in 8 server variant 2 nodes per machine), second - average thr

RE: Node failed to startup due to deadlock

Hi Alexey, Please find the attached sample code to reproduce the deadlock (App should be started first, then wait till cache is locked, then start the App2. App2 will fail to start Ignite) App.java App2.java

Re: Using event to reconnect spring created cache client to server

Hello, I am sorry If I am not being clear, my goal is that, once the client cannot reconect to the cluster as the EVT_CLIENT_NODE_RECONNECTED event is triggered, I want to get a IgniteCache instance so I can re-register a continuous query. however, after the event is trigger if I do a ignite.cache(

JDBC Driver

Just started playing with ignite, trying to put it thru its paces. After successfully starting a cluster node, I started the web agent and headed out to the gridgrain web console host and could see the agent talking to the host. Awesome. Next step was to look at integrating with an existing databa

Re: Using event to reconnect spring created cache client to server

Hey, Which exception threw there? Could you share stacktrace? Does here really client reconnects to the same cluster, or it was after the server node was restarted? Evgenii 2017-11-09 18:34 GMT+03:00 guillMelo : > Hello, > I am sorry If I am not being clear, my goal is that, once the client c

Re: JDBC Driver

Hello! What is the database that you want to integrate with? JDBC driver is a part of database code (sometimes as a separate package). -- Ilya Kasnacheev 2017-11-09 18:46 GMT+03:00 kenn_thomp...@qat.com : > Just started playing with ignite, trying to put it thru its paces. After > successfully

Re: Grid freezing

Is it possible that in dequeuePortionIds you will have the same keys(at least one the same key) for scanCache in different threads? If it's possible, I think it's pretty easy to face a deadlock here with _getCurrentMax(customerMaxCache, queryScan), while I suppose 2 different Scans could have the

Re: Ignite/Cassandra failing to use supplied value for where clause

Why Test1Key.id field is transient? Will it works if you remove transient modifier? Also, please check if you get value for key with 'null' id field. On Thu, Nov 9, 2017 at 5:49 PM, Kenan Dalley wrote: > I don't see how because this is what's in the table. And the code > specifically sets the "

Re: Ignite/Cassandra failing to use supplied value for where clause

Ok. The "transient" keyword was the issue. It was a holdover from something else (a previous example that I was using as my basis for this), most likely. Here are the results from the run once I removed "transient" from all of the fields in both Test1Key & Test1: >>> Read from C* (get). Key: [

Re: Multiple Cluster and Cache Joins

Hi Val, Thanks for the quick response. The reason for separate clusters is separation of duties and maintenance perspective. Thanks Saji -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite-cassandra module issue

Hi Tobias, I created a ticket to fix the issue: https://issues.apache.org/jira/browse/IGNITE-6853 2017-10-25 16:23 GMT+03:00 Tobias Eriksson : > Hi Andrey et al > > I believe I now know what the problem is, the Cassandra session is > refreshed, but before it is a prepared statement is created/us

Re: Ignite-cassandra module issue

Hi Dmitriy, I created a ticket for this: https://issues.apache.org/jira/browse/IGNITE-6853 it will be fixed in 2.4. Thanks, Mike. 2017-11-09 2:35 GMT+03:00 Dmitriy Setrakyan : > Hi Michael, do you have any update for the issue? > > On Thu, Nov 2, 2017 at 5:14 PM, Michael Cherkasov < > michael.c

Re: Question on On-Heap Caching

Hi Dmitriy, 1.We are accessing the data using key-value API's (getAll()) 2. Our data is partitioned in a three server node cluster, but our testcase primarily requests the data through one specific node. Regards, Naresh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Affinity Latency

Hi, What kind of logic you run inside of the affinity-based computation and how many computations do you have running in parallel? — Denis > On Nov 7, 2017, at 10:04 PM, rajivgandhi wrote: > > Hi, > We are seeing higher latency form ignite affinity (single key)/compute > (multiple keys) of 7m

Re: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

Hi, In addition to that you need to enable cache metrics calculation: To enable cache metrics gathering: Set CacheConfiguration.setStatisticsEnabled(boolean) to true for every cache you want to collect the metrics for. Pass a particular EventStorageSpi interface implementation into IgniteConfigu

Re: Unable to connect ignite pods in Kubernetes using Ip-finder

The exception still says that the pod cannot connect to the master. If the connection were successful the master would with a list of all Ignite pods deployed. While now the master simply rejects IP finder’s request: Caused by: java.net.ConnectException: Connection refused (Connection refused)

Re: JDBC Driver

Ignite Web Console - RDBMS integration series might be useful for you: https://ignite.apache.org/screencasts.html — Denis > On Nov 9, 2017, at 8:24 AM, Ilya Kasnacheev wrote: > > Hello! > > What is the database that you want to integrate with? JDBC

Re: Ignite Affinity Latency

Not much - it is basically a filtering operation. The throughput is no more that 200-300 TPS tops -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Using event to reconnect spring created cache client to server

That's the problem, after the call to cache ("my-cache") it just holds, which is quite odd, because the call to get all cache names works normally, but attempting to get the instance fails. I can see from the topology that it connects to the correct cluster. Thanks On 9 Nov 2017 11:55 p.m., "Evg

Re: How can I get Ignite security plugin to work with JDBC thin client?

Hi Caleb, This appears to be a problem with our query execution engine, rather than with thin JDBC driver. I created a ticket to fix it [1]. [1] https://issues.apache.org/jira/browse/IGNITE-6856 On Tue, Oct 31, 2017 at 4:49 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Caleb, > >