Thank you ! I will try this.
2016-05-31 0:34 GMT+08:00 Alexei Scherbakov :
> 1. Yes, for open source Ignite version I see no other way.
> 2. Use node predicate [1] [2] to create cache on desired node.
> After that make the simple program reading from the first cache and
> writing to the second.
>
1. Yes, for open source Ignite version I see no other way.
2. Use node predicate [1] [2] to create cache on desired node.
After that make the simple program reading from the first cache and writing
to the second.
You can instead do backup on disk or into database first.
3. I don't know if such exa
Do you mean I need a separate program to manage the cache?How can I backed
up data to other topology node?Where can I find an example?
Thanks
2016-05-30 22:28 GMT+08:00 Alexei Scherbakov :
> Hi,
>
> 1. You can destroy cache (IgniteCache.destroy) and recreate it dynamically
> with new configurat
Hi,
1. You can destroy cache (IgniteCache.destroy) and recreate it dynamically
with new configuration.
Data must be backed up somethere(on example in the other cache) until the
process is finished.
Don't forget to update Ignite's startup configurations on all server nodes
or you will lose changes
Hi,I have some questions about using Ignite in the production environment.
1、I have 3 Ignite nodes as Server,My Java application uses Ignite as client.
Now,I just use Ignite as JCache implements.
When I want to update the Cache config,like adding indexs,What's the
best way to do it?