Hi Satya,
The main problem here is that Ignite is completely abstracted from the
persistence store by CacheStore interface. It can be any storage -
relational database, disk based key-value storage, MongoDB, HDFS, etc... The
implementation of such trigger will be different for different stores,
Hi Vladimir,
Thank you for your help. I have tested your test case, but it was not worked.
It is failed as the got cache1 is null.
Here is the output result and exception,
[09:23:09,404][INFO ][test-runner][GridDiscoveryManager] Topology snapshot
[ver=1, servers=1, clients=0, CPUs=8,
What I mean by isolation is that they do not try to automatically discover each
other. They only form a cluster manually when triggered.
> Am 01.12.2015 um 13:58 schrieb Denis Magda :
>
> fsapei,
>
> What do you mean under isolation between two different caches?
> All the
Hi all,
We can easily set an expiry policy for any entry. Sorry to Anton and Vladimir
, you are right.
Talk is cheap, show you the code...
the test case
public static void testPut1() throws Exception {
getCache().put("key","val", TimeUnit.SECONDS.toMillis(1));
String val =
Thank you for your idea. Your solution should work.
May it be possible to perform the following operation?
- Create a new cache and isolate it from being replicated with the old cache.
- Populate data on new cache
- Shutdown old cache and remove the new cache isolation.
fsapei
> Am 30.11.2015
Hi Denis,
my scenario is as follows:
- start a node server with the following configuration:
JVM_OPTS="$JVM_OPTS -Xms4g -Xmx4g"
JVM_OPTS="$JVM_OPTS -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB
-XX:NewSize=128m -XX:MaxNewSize=128m"
JVM_OPTS="$JVM_OPTS -XX:MaxTenuringThreshold=0
fsapei,
What do you mean under isolation between two different caches?
All the caches live they own life and don't affect each other.
--
Denis
On 12/1/2015 12:08 PM, Ferry Syafei Sapei wrote:
Thank you for your idea. Your solution should work.
May it be possible to perform the following
Fsapei,
Seems that the cluster breaks down when you execute the queries over 40
million rows. As a result you see partition map exchange related
exceptions. Share the full logs using some file-sharing service.
Analyze your SQL query by paying attention to the following:
- What query do you
Hi Val,
I realize this is not a trivial task but here are a couple of ideas.
1. Triggers that run an offline task outside of the database processes
(perhaps an ignite instance) that sync the cache. Depending on the database,
we could auto-generate the DDL for defining the trigger making it easier
Lin,
As you can see at example you can use cache.withExpiryPolicy() to gain
cache wrapper with specific ExpiryPolicy.
This policy will be used during operations on this cache wrapper, only.
You can create as much wrappers as you need and put/get/etc entries using
them.
I recomend you to use
10 matches
Mail list logo