Re: getAverageGetTime/getAveragePutTime APIs of CacheMetrics always return 0

Hi, Changed to 2.3.0 and added AverageGetTime/AveragePutTime still 0. Per -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Affinity Compute latency

Hi All, We see a significant difference between the latency nos for affnityRun(single key)/compute(multiple keys) and get/getall. Our code is based on the below example:

Re: Affinity Compute latency

Hi, Most likely, first compute call will register a job class and it takes most of time. Make sure your class will not be unloaded between compute calls [1]. Try to make much more cycles to benchmark to make it run a few tens of seconds and add warm-up cycles. You can see how it done in Ignite

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

Hi, I have used API method *TcpDiscoveryKubernetesIpFinder* and set Ip address explicitly as *https://192.168.120.92 using ipFinder.setMasterUrl *. But still I am unable to retrieve ip addresses of running ignite pods. I am using flannel network in kubernetes. Following is the error log I

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

hi All, My server side cache configuration with JDBC storage as back-end. whose data source refer to a bean "serverDatasource" from server spring context. While a pure client node to fetch data from the server, it always report: GridCachePartitionExchangeManager - Failed to process custom

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

Hello Aaron! - In Ignite, client nodes are always aware of backed storage (cacheStoreFactory) of all caches. This is by design. - In Ignite, client nodes perform operations on backed storage DB for transactional caches. The reasoning here is that transaction commit has to happen in one place,

Re: Failed to parse query: exception with Scala

Thanks. I currently do not have indexed types for cache "sharedRDDProducer" as i currently add it as below. *val sharedRDDProducer: IgniteRDD[String, String] = igniteContext.fromCache[String, String]("sharedRDDProducer")* *sharedRDDProducer.savePairs(jsonRdd)* Is the indexed types needed for

Re: Ignite Affinity Latency

Answered in [1] thread. [1] http://apache-ignite-users.70518.x6.nabble.com/Affinity-Compute-latency-tt18028.html On Wed, Nov 8, 2017 at 9:03 AM, rajivgandhi wrote: > Hi, > We are seeing higher latency form ignite affinity (single key)/compute > (multiple keys) of 7ms

Re: Failed to parse query: exception with Scala

Do you have indexed types for cache "sharedRDDProducer"? like cacheCfg.setIndexedTypes(String.class, String.class); Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: write behind performance impacting main thread. Write behindbuffer is never full

Hi Larry, Please note that applyBatch() takes locks after the call to updateStore() while flushCacheCoalescing() takes them before updateStore(). UpdateStore() does all the work with persisting your data via CacheStore, so it is could be quite long & blocking operation for one flushing thread.

Re: Ignite Affinity Latency

Thanks Andrew. The nos are an average (not 90+ percentile) over a period of 60 minutes! We use the default deployment mode which is Shared. We used 3 nodes M4.large instances. Throughput less than 200-300 TPS 1. Are the nos below your expectations? 2. Given the above, what changes are

Re: split-brain problem and GridSegmentationProcessor

Hi Anirudha, we can collaborate on this. Please drop me an email and we can then discuss it. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to parse query: exception with Scala

I don't really get, what you trying to do here: val sharedRDDConsumer = igniteContext.fromCache("sharedRDDProducer") it looks like a mistake Here is example of using ignite sql from spark in java:

Re: Affinity Compute latency

Thanks Andrew. The nos are an average (not 90+ percentile) over a period of 60 minutes! We use the default deployment mode which is Shared. We used 3 nodes M4.large instances. Throughput less than 200-300 TPS 1. Are the nos below your expectations? 2. Given the above, what changes are

Re: Multiple Cluster and Cache Joins

Saji, To do a join caches must reside in the same cluster. What is the reason for creating separate clusters in the first place? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to parse query: exception with Scala

I am just trying to retrieve the already cached shared-rdd( sharedRDDProducer) back from cache. I have also tried like below too without success. *val *sharedRDDConsumer*: IgniteRDD[String, String] = igniteContext.fromCache[String, String]("*sharedRDDProducer*")* I am getting the same error even

Re: Two Ignite Clusters formed after network disturbance

Amit, 1. On all nodes, clients and servers. 2-3. Easiest way is to create a JAR file with these classes and put it under IGNITE_HOME/libs prior to start. This JAR will be automatically picked up. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite-cassandra module issue

Hi Michael, do you have any update for the issue? On Thu, Nov 2, 2017 at 5:14 PM, Michael Cherkasov < michael.cherka...@gmail.com> wrote: > Hi Tobias, > > Thank you for explaining how to reproduce it, I'll try your instruction. I > spend several days trying to reproduce the issue, > but I

Re: Failed to parse query: exception with Scala

Any suggestions on the below will be really appreciated. Thanks. On Wed, Nov 8, 2017 at 11:00 AM, future expert wrote: > I am just trying to retrieve the already cached shared-rdd( > sharedRDDProducer) back from cache. I have also tried like below too > without

Re: Failed to parse query: exception with Scala

I think I found something interesting. I see the below when i print the current topology from visor. [image: Inline image 1] The "1%lo" string that is under the Int./Ext. IPs is the same as the string that is included in the below exception when *sharedRDDConsumer.first() or

Re: same cache cannot update twice in one transaction

No, this is not implemented yet. Here is the ticket where you can track the progress: https://issues.apache.org/jira/browse/IGNITE-3478 -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Out of memory in client node freezes complete cluster

Hi, I am using Ignite 2.0. I have observed that if there is an out of memory error on any Ignite client node, the complete cluster becomes unresponsive. A few details about my caches/operations - 1. Atomicity mode - Transactional 2. Locking - Pessimistic with repeatable read. Is this expected

Re: Ignite Plugin development ...

Hi, I am writing a plugin and have followed the steps mentioned on this conversation but the plugin is not discovered by Ignite node on start up. I have created META-INF/services directories on my Ignite *server* node under the 'libs' directory. I also tried keeping it at the same level as

Multiple Cluster and Cache Joins

Hi Team I have a scenario . I wanted to have two ignite clusters ClusterA will have 2 members and will have a cacheA and ClusterB will have 2 members and will have cacheB. Would I be able to do SQL join of cacheA and CacheB considering the fact that it is in two isolated clusters in same

Re: Question on On-Heap Caching

Hi, Ignite always stores data off-heap. Enabling on-heap caching just turns Java heap into a cache for the off-heap memory, allowing you to configure eviction policies specific for such a heap cache. I believe the idea is

RE: Node failed to startup due to deadlock

Hi Alexey, Thank you for pointing out the problem with caches causing deadlocks. I fixed the classpath pointing to 1.9, but the issue still exists. Actually we could reproduce deadlock with a scenario when two nodes trying to comeup during same time, and the first node holds lock on a cache.

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

Got it thanks Ilya! So if we try to totally isolate the client from server, may need start a facade to supply query only service. Regards Aaron aa...@tophold.com From: Ilya Kasnacheev Date: 2017-11-08 19:57 To: user Subject: Re: When client node query a cache with JDBC storage, report

Re: Question on On-Heap Caching

Thanks Alexey for the info. Actually our application is read-heavy, and we are seeing high latencies (based on our perf benchmark) when we are measuring the response times during load tests. Based on the one of the thread's recommendations

Re: Question on On-Heap Caching

Naresh, several questions: 1. How are you accessing data, with SQL or key-value APIs? 2. Are you accessing data locally on the server or remotely from a client? If remotely, then you might want to enable near caching. D. On Thu, Nov 9, 2017 at 3:01 PM, naresh.goty

Re: Ignite Plugin development ...

Previous example was done with 1.0 . It work also in 2.0. Be aware of definition within META-INF/services/org.apache.ignite.plugin.PluginProvider and implementation itself. Ex. #SecurityPluginProvider comment line ro.myset.appcore.grid.plugins.security.SecurityPluginProvider Output log... ...