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/

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/

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=10=45=zeppelincache;)

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

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: 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/

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.

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

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:

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

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

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

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: 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

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}"/>

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.

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

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: 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

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