Re: "ArrayIndexOutOfBoundsException" happened when doing qurey in version 1.6.0

Hi, The exception looks truncated as it ends with 'Caused by: java.lang.ArrayIndexOutOfBoundsException'. Can you please provide the whole trace? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-happened-when-doing-qurey-in-ver

Re: Update performance

Hi Ionut, What level of transactional guarantees are you expecting? Generally, it sounds like you can try utilizing EntryProcessor [1] which allows not to move the data from servers to client before updating. invoke() operation can be enlisted in a transaction in the same way as put(). Let me kno

Re: How to set isolated Ignite Clusters by java API

After I setted "Ignition.setClientMode(false);" and setted gridname to Ignite instance, It is OK! Thanks anyway. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-set-isolated-Ignite-Clusters-by-java-API-tp6221p6247.html Sent from the Apache Ignite Users ma

Re: index/exposing SqlField on a composition object?

Hi Binti, No, you can't do that. You should store Order and Trade separately in Ignite as well and join these two table when needed. Basically, it sounds like you don't need to change the data model at all when moving from DB to Ignite, which means that you can even use SQL queries that you used w

"ArrayIndexOutOfBoundsException" happened when doing qurey in version 1.6.0

Recentely I updated Ignite version from 1.5.8 to 1.6.0 and found some queries failed with the following information. It never happened in Ignite version 1.5.8. Could anyone help me to confirm it? [14:04:45,486][SEVERE][pub-#14%null%][GridMapQueryExecutor] Failed to execute local query: GridQueryR

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Resources including application context are injected in factories as well. Note that Ignite node has to be started either with Spring configuration file (Ignition.start("ignite-cfg.xml")) or using IgniteSpringBean: -Val -- View this message in context: http://apache-ignite-users.70518.

index/exposing SqlField on a composition object?

Hi, If we have a cache that contains Order objects which has a set of Trades, is it possible to query the cache on some fields from the Trade object or search ? The cache is IgniteCache class Order { /* class variables */ // some key fields private Set trades; } Here the tables are

Re: sql query large data set which is larger than memory

Hi, Swap space means that whatever data you need to execute the query needs to be unswapped first. In other words, if you do query like 'select * from', it will not help. But if it has a reasonable condition that will allow result set to fit in memory along with all other data, you will not run ou

Re: transaction not timing out

If in any case commit() is unable to finish, how can we catch that? in an optimistic transaction, it should not even reach the commit phase using the 2 phase protocol. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/transaction-not-timing-out-tp5540p6241.html Se

Re: How does it ensure that the primary partition has already synchronized to backup partition when during rebalance

Hi, The answers are inline: Hi, all > I am researching the cluster rebalance, and the sync mode > is CacheWriteSynchronizationMode.PRIMARY_SYNC, when rebalance completed, > how does it ensure that the primary partition has already synchronized with > backup partition because it possible ha

Re: Performance in case of 1 server node

Hi Denis, I will remove startSize. Is there any need to add or remove anything? Before,I used JCache(JSR 107). Now instead of it I use Ignite(one node). And want to get better performance. Also, I use read-through cacheLoaderFactory(in MutableConfiguration) for cache configuration,and not Ignit

Re: Performance in case of 1 server node

Hi, I would suggest removing the “startSize” at all. Don’t think that it will affect your performance significantly. However why are you interested in benchmarks of a single node scenario with a local cache? What you’re going to compare Ignite with? — Denis > On Jul 11, 2016, at 2:55 PM, dani

Re: Create cache configuration error

Hi, Index field name must be unique across both a key and a value. Check the implementation of your key and value and make sure that there is no duplicates. — Denis > On Jul 12, 2016, at 5:01 AM, deleerhai <185961...@qq.com> wrote: > > Hi, > Create cache configuration error. > >

Re: Cache Partitioned Mode

Correct. — Denis > On Jul 11, 2016, at 7:03 PM, daniels wrote: > > -"it will load it from the cache store, puts into memory and returns for the > client. " > > It means that load occurrs on server node by server node loader (and not by > client node loader)and then puts in memory on server s

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, Can you also send me your ignite libraries from the /usr/local/lib/libignite* ? That would be helpful for analyzing core dump as I seem to have different gcc version. Best Regards, Igor On Tue, Jul 12, 2016 at 5:50 PM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > H

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, Thanks for the information. Sorry for the confusion caused, We are running this test case as the first time with ODBC in 1.6.0. We never tried this test scenario with ODBC earlier. Yes, We are creating a new connection for every thread. Please find the attached core dump. Please sugge

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, I'm a little confused here, as you are telling you used the same test for the 1.5.0 and for the 1.6, but for the 1.5.0 you didn't use ODBC and for the 1.6 you do. How could this be possible? Have you modified your test to use ODBC on 1.6? Do you use the same ODBC connection concurren

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, Yes, this test is executed with ignite 1.5.0 release version without ODBC. I could see there is no code dump files generated in our executable path. Could you please suggest the configuration which you need for test. We are using our client project for testing this scenario. Thanks i

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, You said you were running the same test on 1.5.0. But 1.5.0 does not include ODBC driver. Were you using one of the nightly builds? Also, it would be very useful if you could provide either your test or segfault core dump. Best Regards, Igor On Tue, Jul 12, 2016 at 2:21 PM, Agneesw

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, Yes, we have used the ODBC to test this scenario. Please. Thanks, Agneeswaran -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6230.html Sent from the Apache Ignite Users mailing list archive at N

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran, Do you use ODBC for these tests? Best Regards, Igor On Tue, Jul 12, 2016 at 1:45 PM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > Hi Igor, > > We are running the same query or different query on parallel for concurrent > test using Ignite ODBC node to check the dat

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor, We are running the same query or different query on parallel for concurrent test using Ignite ODBC node to check the data retrieval time but we are end up with the Segmentation fault as the processors gets interrupted/stopped. We are unable to execute the same or different query on paral

Re: sql query large data set which is larger than memory

off-heap memory is also in RAM. The data set is larger than RAM. If it's possible to put cache in swap space and do sql operations while some cache data store in swap space? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/sql-query-large-data-set-which-is-larger

Re: Create cache configuration error

Hi deleerhai Could you show source and class hierarchy for ContractInfo. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Create-cache-configuration-error-tp6218p6226.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite used memory 7 times greater than imported data

Hi, everyone I meet a problem: Ignite used 220G+ memory, but the imported data is only 31G. Why? Basic info: I used Ignite 1.6, and deployed ignite cluster using 2 machine whose memory is 128G. I run 3 ignite instance in every machine. I am using JDK8. I has 31G data in csv fil

Re: sql query large data set which is larger than memory

HI November, Please look at memory parameters JVM_OPTS for server nodes. Try to use off-heap memory for cache [1] [1] http://apacheignite.gridgain.org/v1.5-b1/docs/off-heap-memory -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/sql-query-large-data-set-which-i

Re: How to set isolated Ignite Clusters by java API

Hello, I think you need to change range ipFinder2.setAddresses(Arrays.asList("127.0.0.1:48500..48520")); and ipFinder1.setAddresses(Arrays.asList("127.0.0.1:49500..49520")); from Ignite instances. Because first instance (discovery SPI) starts on range 48500..48520 and second - on 49500..49520 Ig

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Agneeswaran, Can you please clarify what kind of test are you running and what kind of an issue are you facing? What does the test do exactly and what kind of behavior do you observe? Are the any exceptions? Best Regards, Igor On Tue, Jul 12, 2016 at 4:26 AM, Agneeswaran < agneeswaran.ponnura

How to set isolated Ignite Clusters by java API

I followed the guide about "Isolated Ignite Clusters on the Same Set of Machines", I tried to use xml to start ignite, it is OK. but when I tried to use java api to start ignite, it failed with the following info "[09:42:47] Failed to connect to any address from IP finder (will retry to join topo

How does it ensure that the primary partition has already synchronized to backup partition when during rebalance

Hi, all I am researching the cluster rebalance, and the sync mode is CacheWriteSynchronizationMode.PRIMARY_SYNC, when rebalance completed, how does it ensure that the primary partition has already synchronized with backup partition because it possible have write request during rebalancing