Re: configuration for some persistent and some non-persistent caches

Create a data region with persistence enabled and assign required caches to it as shown in this section [1]. Unassigned caches will go to the default region that has persistence off. Or you can create one more region not turning on persistence and assign the rest of the caches there. [1]

configuration for some persistent and some non-persistent caches

How do you configure some caches to be persistent and others not, on the same cluster? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Inconsistency reading cache from code and via REST?

Hi Michail, Could you please provide next information: 1)Ignite version 2)your ignite xml config 3)your reproducer (GridCacheTest). Looks like it wasn't attached. Also if you are using Ignite 2.4 then do you add your servers to baseline topology using control.sh before cluster activation?

Re: Apache ignite support for multi-tenancy

Hi, You can create several separated caches per tenant with the same configuration. What is your use case? Thanks, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Inconsistency reading cache from code and via REST?

My Setup in windows - all running locally pointing at same ignite xml config - 2 * ignite servers running ignite.bat - Provided java sample code GridCacheTest (running in IntelliJ) to put 20 key value pairs in a cache The sample code runs correctly and outputs the key/value pairs it reads

Apache ignite support for multi-tenant

Will there be support for multi-tenants in Apache Ignite? I know grid gain support multi tenancy . Can this be achieved in apache ignite in some ways? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to create instance of CacheManager of ignite

Val Ignite ignores the default URI configurations, discoverySpi to be more specific. If I add any discovery to default-config.xml, ignite client ignores it. I was able to make it work by using a different configuration file name my-ignite-config.xml Thanks -Arvindo -- Sent from:

Re: Efficiently determining if cache keys belong to the localservernode

> How does Ignite ensure requests consistency during rebalancing? Basically, sorts of locking and some retry-on-failure handling. Ignite will make sure that all operations on a partition are finished before moving/evicting it, and will try to switch to another node if the first node that it tried

Re: Docker deployment with EXTERNAL_LIBS environment variable

Hi Petr, I've mentioned you in the ticket. Is it obvious change so we could apply patch? Or could you advise maintainer/expert here? Sincerely, Dmitriy Pavlov ср, 18 апр. 2018 г. в 7:27, Roman Shtykh : > I had the same problem (pretty common not having -i option) and fixed

Re: How to start Ignite with a jar built from the source code

Hi, You can find ignite.bat and ignite.sh scripts in source bundle bin folder. It is the best way to start Ignite with custom configuration. It described here: https://apacheignite.readme.io/docs/getting-started#section-passing-configuration-file Also you can take a look inside these scripts

Re: Ensuring CacheStore Operations Finished

I've checked some details and found out that Cache.destroy future will be completed only after all changes are flushed to a persistent storage. This way Cache.destroy() call completes when synchronization is already finished. Best Regards, Roman -- Sent from:

Re: Can not create Affinity Key

Ilya, Thanks a lot for your help. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to start Ignite with a jar built from the source code

Hi Am using 2.4 I would like to build jar from source code downloaded from Apache and use jar to start the Ignite node, do we have any documentation on this on how to pass the config XML etc.. Thanks Naven -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache.clear() is not clearing the data in DB when both native as well as 3rd Party persistence is used

Hi Naveen, Cache.clear() does not delete records from 3rd Party Persistence. According to documentation you can use Cache.removeAll() [1]. Best Regards, Roman [1] https://apacheignite.readme.io/docs/3rd-party-store#section-loadall-writeall-deleteall- -- Sent from:

Re: Ensuring CacheStore Operations Finished

Hi Roman. We use write-behind for performance considerations. We cannot use write-through for that reason. Regards. On Wed, Apr 18, 2018 at 9:59 AM, Roman Guseinov wrote: > Hi Alper, > > To make sure that all cache changes propagated to 3rd Party Persistence > please

Re: Ensuring CacheStore Operations Finished

Hi Alper, To make sure that all cache changes propagated to 3rd Party Persistence please enable Write-Through option [1] and disable Write-Behind. Write-through means that the data will be automatically persisted whenever it is updated in the cache. Best Regards, Roman [1]

Cache.clear() is not clearing the data in DB when both native as well as 3rd Party persistence is used

HI AM using 2.4 with dual backing store. When we use cache.clear, cache entries are getting deleted, however entries in DB are not getting deleted., We are using Oracle as backing store along with Ignite native persistence. However, all the individual upserts/deletes we do they Key Value API

Ensuring CacheStore Operations Finished

Hi all. My use case is as follows: - Create a cache A that synchronizes with DB table A_TABLE - Destroy A and backup A_TABLE as A_TABLE_BCK At the moment between destroy and backup is there a way to know that all the synchronization was finished and the A_TABLE is not incomplete? Regards. --