Re: Query execution is too long warning while running Yardstick-ignite

Great result. When I changed thread count to *8* as per your suggestion, 'long running' warning messages disappeared. Thank you so much for your promt support. -- View this message in context:

How to set the value of RebalanceThreadPoolSize?

According to the document, RebalanceThreadPoolSize is Max count of threads can be used at rebalancing.When setted to 1 will has minimal impact on the operation of the grid. But my test result is the opposite. For example, in my test, if I set RebalanceThreadPoolSize to 1,it will affect normal

Re: Load data to cache

Hi, I have not installed JDBC driver. Is it need to load data from store even I enable ODBC driver in Spring XML file? I don't know whether Cache configuration is correct or not. Can you Please see my Spring XML configuration file? If anything wrong in this, Please let me know.

Re: max size on cache

Thanks, Val. On Tue, Mar 28, 2017 at 5:49 PM, vkulichenko [via Apache Ignite Users] < ml-node+s70518n11524...@n6.nabble.com> wrote: > Hi Rishi, > > Eviction policies allow to specify limits: https://apacheignite.readme. > io/docs/evictions > > -Val > > -- > If you

Server Client Connection

Hi I have created 5 server nodes in 5 jvm process in 3 jvms. After the client node has started up, the oldest server node will establish a connection to the client node through client's communication port (471XX) periodically. May I know the reasons for this? if it is because of Leader

Re: max size on cache

Hi Rishi, Eviction policies allow to specify limits: https://apacheignite.readme.io/docs/evictions -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/max-size-on-cache-tp11523p11524.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

max size on cache

Hi Val, How can I put a max size on cache ? could not find any property in Cache Configuration OR I missed something. Thanks, Rishi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/max-size-on-cache-tp11523.html Sent from the Apache Ignite Users mailing list

Re: Cache get using sub-fields of composite key

To execute get() you need the whole key object that will be equal to the one used for update. To query by one of the fields you can use SQL: https://apacheignite.readme.io/docs/sql-grid -Val -- View this message in context:

Re: Insert data in hdfs using ignite

Prashant, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. Prashant Singh wrote > This problem is resolved now.

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

cross-posting to dev list. Guys, Does anyone have an idea why client mode in Visor affects behavior? I thought we already forced client mode there, no? Alexey, you should know the answer. Can you please take a look at this thread? -Val On Tue, Mar 28, 2017 at 7:02 AM, ght230

Re: Distributed Closures VS Executor Service

kmandalas wrote* > One question is * > : if some Job fails and other Jobs belonging to the same Task are still > running (in the same or other grid nodes), is it possible to cancel them > and abort the whole Task before waiting for all of them to finish? This will happen if result() method throws

Re: Distributed Closures VS Executor Service

-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11517.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Does operations through entry processor blocks the regular GETs?

As Denis mentioned, entry is locked while entry processor is executed, so you can't read it. Entry processor is supposed to be as lightweight as possible, you should avoid putting heavy long-running logic there. -Val -- View this message in context:

Re: 2.0

Hi Dimitry Yes I think that would work and will give a go. Thanks Lea > On 28 Mar 2017, at 6:51 pm, Dmitriy Setrakyan wrote: > > Thanks Denis! > > Lea, I just want to clarify that if you manually pick Denis' commit, it will > likely fix your issue, but it will not be

Cache get using sub-fields of composite key

Hi, I have composite key object of more than one fields(f1, f2) for my cache. Now I want to get cache values using cache.get() based on either using f1 or f2(not using both f1 and f2). How can I do this? Thanks. -- View this message in context:

Re: 2.0

Thanks Denis! Lea, I just want to clarify that if you manually pick Denis' commit, it will likely fix your issue, but it will not be an official Ignite release and will not have undergone the regular testing and QA cycle that all Ignite releases generally go through. D. On Tue, Mar 28, 2017 at

Re: PriorityQueue\SortedList in ignite

Hi Ken, As far as I know there are no plans for these features. However, if you're willing to contribute then the task can be designed with the help of the community so that you can complete it faster. What do you think? -- Denis -- View this message in context:

Re: Load data to cache

Hi, Go to this [1] documentation section and click on CacheJdbcBlobStoreFactory tab in the example section. [1] https://apacheignite-cpp.readme.io/docs/cache-store#section-read-through-and-write-through

Re: 2.0

Lea, If you can’t wait for 2.0 release I would suggest you pick my commit, merge it to your fork of Ignite 1.9 release and build it from sources. Does it work for you? — Denis > On Mar 28, 2017, at 1:21 AM, Lea Thurman wrote: > > Thanks Pavel > > Would it be

Re: Query execution is too long warning while running Yardstick-ignite

Also could you decrease count of thread to 8 and check that will you have long running queries? For it need to change -t argument: set CONFIGS=^ -cfg %SCRIPT_DIR%\..\config\ignite-localhost-config.xml -b 1 -w 60 -d 300 *-t**8* --server -sm PRIMARY_SYNC -dn IgniteSqlQueryBenchmark -sn IgniteNode

Re: Query execution is too long warning while running Yardstick-ignite

Hmm... It's strange. Could you share log files and results-* folders? On Tue, Mar 28, 2017 at 9:47 AM, ronyjohn wrote: > Yes I got same kind of message from ThroughputLatencyProbe.csv file. > > --Probe dump file for probe: >

Re: Does operations through entry processor blocks the regular GETs?

Is there any functionality in Ignite which allow to read stale data while writes are getting executed using entry processor. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Does-operations-through-entry-processor-blocks-the-regular-GETs-tp10370p11505.html Sent

Re: Load data to cache

Where I add dataSource bean? I mean,need to add in code or Spring XML file? Can you please provide me an example for this? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Load-data-to-cache-tp11394p11504.html Sent from the Apache Ignite Users mailing list

Re: Logging ignite-log4j.jar

Hi Sam, I see you've cross-posted this as comment to ticket. I've already made a fix regarding your suggestion and reposted this to dev-list. On Fri, Mar 24, 2017 at 9:25 PM, javastuff@gmail.com < javastuff@gmail.com> wrote: > Thanks Andrey. > > Looked at code and seems like check for

Re: Load data to cache

Seems like you have not set dataSource bean for your store so it does not know how to establish connection to your database. I believe, you need add dataSource bean (javax.sql.DataSource) for your store. Best Regards, Igor On Tue, Mar 28, 2017 at 3:43 PM, kavitha wrote:

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

Yes,I use custom build. Today I tried to set Ignition.setClientMode(true) for command "open" of the visorcmd. It seems the visorcmd will not stuck the whole cluster again. Is there anything wrong in "ClientMode" of the visorcmd? -- View this message in context:

Re: Load data to cache

javax.cache.integration.CacheLoaderException: Failed to load cache: NORTHWND at org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.loadCache(CacheAbstractJdbcStore.java:848) at

Re: Load data to cache

Can you provide full exception details, including inner exception? On Tue, Mar 28, 2017 at 3:34 PM, kavitha wrote: > Yes I tried. But I got below exception. > > An unhandled exception of type > 'Apache.Ignite.Core.Cache.Store.CacheStoreException' occurred in >

Re: Load data to cache

Yes I tried. But I got below exception. An unhandled exception of type 'Apache.Ignite.Core.Cache.Store.CacheStoreException' occurred in Apache.Ignite.Core.dll Additional information: Failed to load cache: NORTHWND -- View this message in context:

Re: Load data to cache

Looks like Igor is right, these store arguments do not make sense. Try "cache.LoadCache(null)". On Tue, Mar 28, 2017 at 3:09 PM, kavitha wrote: > > SQL version 12.0.2000.8 > Ignite version 1.9.0. > I am using ODBC driver , not installed JDBC driver. > > > > > -- > View

Re: Load data to cache

SQL version 12.0.2000.8 Ignite version 1.9.0. I am using ODBC driver , not installed JDBC driver. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Load-data-to-cache-tp11394p11496.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Load data to cache

Well, I do not have experience working with the store you use, but you pass .NET types as arguments for a Java store. This does not seem like this is going to work. I may be mistaken though. But even if these were Java types they do not look like a valid arguments for this store. Have you tried

Re: Load data to cache

Hi! Could you tell us exact version of MS SQL server and exact version of JDBC driver? And Ignite version. We will try to reproduce your issue. On Tue, Mar 28, 2017 at 6:37 PM, kavitha wrote: > SQL database > > > > > -- > View this message in context:

Re: Load data to cache

SQL database -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Load-data-to-cache-tp11394p11493.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Load data to cache

Hi, Which database do you use? Best Regards, Igor On Tue, Mar 28, 2017 at 7:57 AM, kavitha wrote: > Hi, > > I tried following code to load cache. Could you please correct the code, If > It is wrong? > > IIgnite ignite = Ignition.Start(@"F:\Visual >

Re: Distributed Closures VS Executor Service

Hello Christo, After checking in more detail the options we have with Ignite, our first user case and feedback we have so far (e.g. feedback from Dmitry here: http://apache-ignite-users.70518.x6.nabble.com/Distributed-callables-passing-data-and-getting-back-results-td11224.html), we conclude that

Re: 2.0

Thanks Pavel Would it be worth us reverting to an earlier release. Any idea when it was introduced? Regards Lea Thurman. On 28 March 2017 at 08:46, Pavel Tupitsyn wrote: > According to the dev list thread (http://apache-ignite- >

Re: 2.0

According to the dev list thread ( http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-td15690.html ), you can expect 2.0 by the end of the April. On Tue, Mar 28, 2017 at 10:41 AM, Lea Thurman wrote: > Hi all, > > We have upgraded to 1.9

2.0

Hi all, We have upgraded to 1.9 and noticed the following issue: https://issues.apache.org/jira/browse/IGNITE-4858 I understand this is to be fixed in 2.0. Is there any indicated when this is planned to be released? Regards Lea Thurman -- *Lea Thurman* OneSoon Limited Manchester Business

Re: NullPointerException when using IGFS

Hi, Thanks for testing, hadoop specialists will fix it. Please use sequentialReadsBeforePrefetch = 64 as a workaround for now. Thanks! -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-when-using-IGFS-tp11328p11486.html Sent from

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

Hi, Do you use custom build? In logs Ignite version 1.6.12, but it uses stripped pool, which was introduced only in 1.8.2 and 1.9. Also there was a node stall, because of many disk operations (swap file). This doesn't lead to hang, but may reduce cache performance. Besides log files also thread

Re: Query execution is too long warning while running Yardstick-ignite

Yes I got same kind of message from ThroughputLatencyProbe.csv file. --Probe dump file for probe: org.yardstickframework.probes.ThroughputLatencyProbe@12941d84 (class org.yardstickframework.probes.ThroughputLatencyProbe) --Created Tue Mar 28 12:00:45 IST 2017 --Benchmark config: