Re: Data Nucleus plugin extensions aren't loaded by the grid class loader

I've attached the log from the node, it contains also the exception apache_ignite_jdo_error.txt The executed code in the task is: . //properties with persistence manager factory class and database conne

Re: Eviction Events with offheap values

Andrey, thanks for the clarification. Abraham, it seems EvictionPolicy is not appropriate solution for your case. BTW, why user session expiration logic is related to cache size ? In case user sessions expire by timeout the more appropriate solution would be listening to EVT_CACHE_OBJECT_EXPIRED e

Re: Cache Refresh Options

Hi, Ignite has no build in scheduling capabilities. However, it's very easy to add them to your application. Just deploy service[1] to your server node and use something like ScheduledThreadPoolExecutor for running load task on schedule. Did this help? [1] https://apacheignite.readme.io/docs/ser

Re: Cache Refresh Options

Ignite does have built-in scheduling capabilities, please see https://apacheignite.readme.io/docs/cron-based-scheduling Pavel. On Mon, May 16, 2016 at 11:52 AM, Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > Hi, > > Ignite has no build in scheduling capabilities. However, it's very e

Re: Cache Refresh Options

Cool, didn't knew what 2016-05-16 12:00 GMT+03:00 Pavel Tupitsyn : > Ignite does have built-in scheduling capabilities, please see > https://apacheignite.readme.io/docs/cron-based-scheduling > > Pavel. > > On Mon, May 16, 2016 at 11:52 AM, Alexei Scherbakov < > alexey.scherbak...@gmail.com> wrote

Re: Cache Refresh Options

It sure does. Thanks. On May 16, 2016 4:52 AM, "Alexei Scherbakov" wrote: > Hi, > > Ignite has no build in scheduling capabilities. However, it's very easy to > add them to your application. > Just deploy service[1] to your server node and use something > like ScheduledThreadPoolExecutor > for ru

Re: Cache Refresh Options

Awesome. Thanks much Pavel. On May 16, 2016 5:01 AM, "Pavel Tupitsyn" wrote: > Ignite does have built-in scheduling capabilities, please see > https://apacheignite.readme.io/docs/cron-based-scheduling > > Pavel. > > On Mon, May 16, 2016 at 11:52 AM, Alexei Scherbakov < > alexey.scherbak...@gmail.

Re: Client Connection to Ignite takes time

Hi Arthi, Yes, there is a dedicated documentation created for Ignite C++ API. Please refer to it for more details: https://apacheignite-cpp.readme.io/docs/ — Denis > On May 11, 2016, at 12:01 PM, arthi > wrote: > > Thanks Denis. > > I think we sho

Re: Ignite Still waiting for initial partition map exchange problem

Hi Kevin, > My first observation is that, the client side keeps running without doing any > write through actions to the database; Client does write-through to a database only if it’s a coordinator of an Ignite transaction or writes to a transaction cache. In other cases server nodes are respo

Re: Get client node instance

Hi Arthi, In current implementation, node instance (i.e. Ignite instance) can not be shared between different processes. Can you describe your use case a bit more? Which start up time would be acceptable in your case? Are you starting client node on the startup of the application or are you starti

Re: Clear cache from Visor throws an exception

Have you tried the latest nightly? Has the issue disappeared on your side? — Denis > On May 11, 2016, at 9:23 PM, zshamrock wrote: > > Could it be because of the cache store implementation classes I use? That > some of them trigger this exception? > > I will try the latest nightly build you've

Re: Ignite Deadlock

Hi, First of all, what is the reason of why you need to interact with caches using JNI? Probably we could recommend you some other approach that is simple and safer. Second, it’s hard to tell why ignite1 gets into a deadlock without the following: - logs from all the nodes; - thread dumps of a

Re: Custom GridSecurityProcessor plugin question

Hi Anand, GridSecurityProcessor.authenticateNode(…) has to be called on your side. Please double check that GridSecurityProcessor.enabled() returns true. If it returns true then your GridSecurityProcessor will be registered in GridDiscoveryManager.start() method. If this doesn’t happen please

Re: Get client node instance

Hi Igor, this is my usecase - I use the ignite data grid to store my business data in memory. My client application needs to run SQL queries on this data. Every client request in the application will be translated to multiple SQL queries. The application needs to support 400-500 concurrent users.

Re: Get client node instance

I mean startup of the client application. Best Regards, Igor On Mon, May 16, 2016 at 7:18 PM, Igor Sapego wrote: > Arthi, > > Why do you create one client node per user request? Can you create > a node on application start and then just use this node instance when > you need to make a request?

Re: Get client node instance

Hi Igor, Yes, I can, but, how do I get handle to the client node instance when a new user request comes in? Each user request invokes the C++ dll. Thanks, Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Get-client-node-instance-tp4897p4963.html Sent from

Re: Get client node instance

Arthi, Why do you create one client node per user request? Can you create a node on application start and then just use this node instance when you need to make a request? Best Regards, Igor On Mon, May 16, 2016 at 6:41 PM, arthi wrote: > Hi Igor, > > this is my usecase - I use the ignite dat

Re: Unexpected performance issue with SQL query followed by error

Hi, I think your query should be rewritten for correct index usage. Ignite has some known pitfalls concerning index usage [1]. Also, join order is sensitive to index configuration. FIrst specify joins using indexes. Could you provide your business model pojos and current indexes configuration? [

Re: Get client node instance

Arthi, It seems to me like we have some misunderstanding here. Let me provide my understanding of your usecase so you could correct me if I'm wrong. You have the client application which is written in C++ and has to handle multiple concurrent requests from multiple users. Now, do you invoke the

Re: Get client node instance

Hi Igor, we invoke it by some other application every time the user needs to make request and then its terminated Thanks, Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Get-client-node-instance-tp4897p4967.html Sent from the Apache Ignite Users mailing l

Ignite Aggregation query

Currently we need to aggregate (group by) data which is distributed on Ignite partitioned cache. What is the best practice do such aggregation on such data grid, For example, by passing SQL group by clause as scanQuery or using compute affinityRun or mapReduce etc. Please advise. Thanks -- View

Re: Ignite Deadlock

Unfortunately, I don't have the problematic instance running anymore, so I cannot provide the logs or thread dumps. I will wait for a week for release of version 1.6, and I hope it will resolve this issue. If I manage to reproduce the problem, I will add the logs. Thanks. -- View this message

Re: Get client node instance

Arthi, Well, there would be significant performance gain if you would not start new client process for every request and then terminate it but rather start node once in the same process that currently starts new process. I'm not sure if it's possible for you. What is the language of the applicatio

Re: Ignite Aggregation query

As side note, currently when we do such aggregation using Oracle database, we put all the keys for the records that needs to be aggregated into some session based global temp table and do a join with original table. What is the best way to achieve such aggregation using Ignite? -- View this mes

Re: Ignite Aggregation query

Ignite SQL queries are ANSI-99 compliant and do support “group-by” clause. I think this is the most natural way to achieve your use case. You can find more information on Ignite SQL queries here: https://apacheignite.readme.io/docs/sql-queries D. On Mon, May 16, 2016 at 11:41 AM, diopek wrote:

Re: Custom GridSecurityProcessor plugin question

Hi Denis Thanks! I was doing two things wrong. GridSecurityProcessor.enabled() was returning false and my security processor implemented both DiscoverySpiNodeAuthenticator and GridSecurityProcessor Once I fixed both, authenticateNode was getting called. I think for my requirements (prevent a

Re: Ignite Aggregation query

Can you please advise, which SQL group-by query would be better practice, perform better? (1) *select A, B, SUM(C) from MyCache where MyCache.id IN () group by A, B* or, (2) by first storing IDs to be joined into some temporary cache as setting ID as affinity key to co-locat

Re: Clear cache from Visor throws an exception

Hi, Denis. Not yet. Will try to test it tomorrow. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Clear-cache-from-Visor-throws-an-exception-tp4848p4975.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can't stop Ignite instance using Ignition.stopAll() or Ignition.kill() until writeBehindFlushFrequency passed

And then it is hanging for about 5 minutes after each IT case. Does the picture above help somehow? How I can do a thread dump? I've tried to use jstack, although could not find anything meaningful in the report it ha

Re: Ignite Aggregation query

Both should work, but the 1st one does not require creation of a temporary table, so prefer the 1st one. On Mon, May 16, 2016 at 1:12 PM, diopek wrote: > Can you please advise, which SQL group-by query would be better practice, > perform better? > > (1) > *select A, B, SUM(C) from MyCache where

Re: Ignite Aggregation query

Ignite has any restriction for the maximum number of tokens to be used within IN (...) clause as Oracle IN clause does? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Aggregation-query-tp4968p4978.html Sent from the Apache Ignite Users mailing list archiv

Re: ODBC Driver and Reporting Tool Usage

Hi Dillip, I think it would be possible, but I am not sure if anyone in the community will have time to get to it soon. Would you be interested in contributing something like this? I think a video of Ignite with Tableau will be extremely useful. D. On Sat, May 14, 2016 at 5:01 AM, Dillip Sahoo

Re: Client Connection to Ignite takes time

The documentation currently does not look complete for the upcoming 1.6 release. We should add version 1.6 of the documentation and add Transactions and other CPP improvements there. Igor, given that you are contributing most of the CPP functionality, do you think you can update the docs? D. On

Re: Cache Refresh Options

Murthy, would setting a simple TTL for entries work for you? Here is more info: https://apacheignite.readme.io/docs/expiry-policies D. On Fri, May 13, 2016 at 2:03 PM, Murthy Kakarlamudi wrote: > Hi, >What are my options to refresh ignite cache from underlying persistent > store on a sched

Ignite non unique table mapping problem

Hi there, I am trying to import a table which has no unique index, so there will be one key to many values mapping. I am wondering is there any support of such situation. I know that in redis, I can use zadd( score, value) to store a list as value. But I did not see any similar support in Ignite.

Re: Get client node instance

thanks Igor, The application is in C++. I was hoping if I could create a shared memory with ignite instance and share it with other process that get trigged on user requests. Is this a possibility? The developer tried it, but seems like it did not work. May be we are missing something. Let me kno

Re: Get client node instance

Hi Igor, I was wondering if the ODBC driver that will come up in v1.6 is thread safe? Can we do a connection pooling using this driver from our calling application level? I am just trying to see if we can go with the ODBC driver to connect to the grid instead of the c++ client API. Thanks, Arthi

Re: Ignite Aggregation query

There is no limitation (other than java heap size) but it must be some sane number if you want to have sane performance. BTW, you can find these docs helpful: https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations Sergi 2016-05-17 2:45 GMT+03:00 diopek : > Igni

IgniteCache method replace(key,newVal) behave different with replace(key,oldVal,newVal)

Are there some different between the IgniteCache two replace methods? In my test: If I call the replace(key,newVal),it's ok. but if I call replace(key,oldVal,newVal) ,there is an exception throws. org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys (retry update if possib