Upgrading Ignite Persistence from 2.1 to 2.3

Hi, I am currently using version 2.1 of ignite and want to upgrade to latest version 2.3. My application uses Ignite Persistence(org.apache.ignite.configuration. PersistentStoreConfiguration) to persist data. As part of upgrading to version 2.3 do I need to change this to DataStoreConfiguratio

Re: How to identify if the data returned from cache is partial data due to multiple node failures in partitioned cache

Hi, If all nodes, that hold partition left topology, will be thrown event EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST. You can listen to it using IgniteEvents.localListen(lsnr, EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST) Regards, Evgenii 2018-01-11 9:01 GMT+03:00 aMark : > Hi, > > We are usi

Re: 3rd Party Persistence and two phase commit

Hi, Andrey! Actually, data could be persisted not on tx initiating node, but on primary(I.e. we have partitioned cache and local cache) . Additionally, data would be persisted on backup node if you enable the corresponding flag. > 11 янв. 2018 г., в 10:12, Andrey Nestrogaev > написал(а): >

Re: Apache Ignite best practice

Hello Ilya! Thanks for the advice with "JOIN TABLE". Can you recommend something for the configuration and diagnostics of the Apache Ignite cluster? For example, what metrics should I look for when the response time starts to grow? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: String as value problem ?

Hi! Forget about it, it was my fault, when you use a String as a value in a cache (and use indexing), it requires that you have Lucene jar's in the classpath, I didn't have that. Mikael Den 2018-01-11 kl. 00:11, skrev vkulichenko: Mikael, First of all, the trace should contain the cause w

Ignite Persistent Cache DotNet

Hi Team, I am testing Ignite cache persistent configuration on version 2.30. I am experiencing strange behavior and it is not consistent behavior. Could you please suggest me how to configure and test persistent behavior? Thanks and Regards, Hemasundar.

Is the default memory region always there ?

If I use something like the configuration example from the documentation: | name="dataStorageConfiguration"> class="org.apache.ignite.configuration.DataStorageConfiguration"> class="org.apache.ignite.configuration.DataRegionConfiguration"> value="#{500L * 1024 * 1024}"/> Will

Re: 3rd Party Persistence and two phase commit

Hi Aleksey, thanks for info, "/Actually, data could be persisted not on tx initiating node, but on primary(I.e. we have partitioned cache and local cache)/" Ok, but no matter where the data is persisted, there will always be only 1 database connection within the transaction, no matter how many nod

Ignite Upgrade from 1.9 to 2.3

Hi All, We are upgrading from 1.9 to 2.3 and here we are facing some issue In 2.3 we are configuring Data Region as below ` * * * *

Re: Ignite Persistent Cache DotNet

Hi Hemasundar, Can you provide more details? What is not consistent? Is there a reproducer? Thanks, Pavel On Thu, Jan 11, 2018 at 12:53 PM, Hemasundara Rao < hemasundara@travelcentrictechnology.com> wrote: > Hi Team, > I am testing Ignite cache persistent configuration on version 2.30. > I

Re: Ignite Upgrade from 1.9 to 2.3

Ignite native persistence replaces Swapping feature from Ignite 1.x. Use native persistence instead of swapping (remove "swapPath" configuration and enable persistence). "swapPath" setting in Ignite 2.x has different semantics: specifying a "swapPath" makes Ignite use memory mapped file for the da

Re: Is the default memory region always there ?

Default memory region is always there even if you add more user-defined data regions. If you are not going to use it at all and not happy with the memory still allocated to the default region you can specify a smaller amount of memory allocated for the default region as described here

Re: Upgrading Ignite Persistence from 2.1 to 2.3

Hi, In 2.3 some configuration methods are deprecated and will be removed in next major release (ignite-3.0). You can safely continue to use old-style configuration, but of course we recommend to switch to new-style if possible to be able to use new features. I'm not sure 2.3 can support old stora

Re: 3rd Party Persistence and two phase commit

Local store means store, that resides only on one node. No other nodes see it. If you don't have local stores in cluster(only distributed ones), then it will be the only db connection within transaction opened. But If you have local stores, then nodes *could open* their own connections to local st

RE: Upgrading Ignite Persistence from 2.1 to 2.3

Hi Andrey, Thanks for the info. Could you also let me know how to migrate the data from 2.1 to 2.3. Are there any APIs/feature which I can use to do that? From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com] Sent: Thursday, January 11, 2018 5:04 PM To: user@ignite.apache.org Subject: Re: Up

Re: Adding custom processor in Ignite Node

Hi, I am not sure that user-list will be able to help you with such questions. You should discuss the implementation options/details at dev-list (http://apache-ignite-developers.2346864.n4.nabble.com/). Probably, you don't need a custom processor class at all. Anyway: 1. Please have a look at th

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, Can you share your configuration for 1) cache 2) memory region? I see "evicts=0" in your stats that looks very strange. Are you sure you have a configured eviction policy in the data region (policyName=RefData)? Does this cache work fine (evicts some data) without Cache Store enabled? Thank

Problem enabling read-through on cache - no suitable driver

I am trying to enable read-through on my cache as follows: Once I activate my c

No user-defined default MemoryPolicy found

Hi, In spite of setting a defaultMemoryPocliySize I am getting the below warning on starting the node. Is there any other configuration required? WARNING: No user-defined default MemoryPolicy found; system default of 1GB size will be used.

Re: IgniteOutOfMemoryException when using putAll instead of put

Here are the configurations DataRegionConfiguration = (new DataRegionConfiguration) .setName("RefData") .setInitialSize(21 * 1024 * 1024) .setMaxSize(21 * 1024 * 1024) .setPersistenceEnabled(false) .setPageEvictionMode(DataPageEvictionMode.RANDOM_LRU) .setMe

Re: No user-defined default MemoryPolicy found

Hi, I see the same message with 2.1 release. 2.3 does not have it. I will check 2.1 source code later. Do you use 2.1 release? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No user-defined default MemoryPolicy found

ok. I see you are at 2.1. (migrating from 2.1 to 2.3) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Problem enabling read-through on cache - no suitable driver

Hi Thomas, Please make sure that your h2 database is started and required tables are created. You can use the following test as example how to do that (please see, CacheJdbcPojoStoreAbstractSelfTest#beforeTest) https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/igni

Re: Ignite Upgrade from 1.9 to 2.3

Thanks Alexey for quick response. - Tejas On Thu, Jan 11, 2018 at 4:51 PM, Alexey Kukushkin wrote: > Ignite native persistence replaces Swapping feature from Ignite 1.x. Use > native persistence instead of swapping (remove "swapPath" configuration and > enable persistence). > > "swapPath" sett

Invitation: [Webinar] Scale Out and Conquer: Architectural Decisions ... @ Wed Jan 17, 2018 11am - 12pm (PST) (user@ignite.apache.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180117T19Z DTEND:20180117T20Z DTSTAMP:20180112T010357Z ORGANIZER;CN=dma...@gridgain.com:mailto:dma...@gridgain.com UID:7cur73ncgtvjh8v004do9fa...@google.com

RE: No user-defined default MemoryPolicy found

Hi Alexey, Is there any way I can check the total memory being used by the off heap cache? I wanted to confirm if the warning is valid. Sorry that I forgot to mention the version I am currently using. It is 2.1. -Original Message- From: Alexey Popov [mailto:tank2.a...@gmail.com] Sent:

Use SQL to query IgniteRDD with scala at Zeppelin

Hi, Below is my code and result where I am trying to query IgniteRDD through SQL statement with scala at Zeppelin. First I use restful API to put a pair of data(key=10, val=45) into Ignite cache. %python import requests requests.put("http://127.0.0.1:8080/ignite?cmd=put&key=10&val=45&cacheName=ze

Re: Adding custom processor in Ignite Node

Hi Thanks for your response. As you mentioned will try to discuss/take help from the dev-list. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: No user-defined default MemoryPolicy found

Hi, Please have a look at topic below to get an estimation of memory usage: http://apache-ignite-users.70518.x6.nabble.com/off-heap-memory-usage-tc19282.html I will check the warning later, it looks strange to me. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/