Hi Laszlo,
Going by the warning message you see - ”Both Ignite native persistence and
CacheStore are configured for cache …”, what is probably happening is that
you might have enabled native persistence and also provided a
CacheConfiguration with a cache factory that can both read and write from
a
Hi Tomislav,
1) When you say you want to increase the heap memory to Ignite node, do you
mean off-heap or on-heap?
To increase the off-heap memory, please make sure to set these parameters
explicitly in your ignite server xml configuration file under the
DataRegionConfiguration that you are curre
Hi Yann,
Event listeners in Ignite can be helpful to you -
https://apacheignite.readme.io/docs/events
You can listen for specific types of events (like cache put, cache read) on
a local node or remote events on a group of cluster nodes and then perform
whatever actions you want.
All the different
Replace the 2 with searchKey
On Fri, Jan 25, 2019, 12:12 PM Karun Chand Hey Andrew,
>
> I think this is what you are looking for -
>
> class Foo {
> int id;
> }
>
> class CustomIgniteBiPredicate implements IgniteBiPredicate List> {
> int searchKey;
>
>
Hey Andrew,
I think this is what you are looking for -
class Foo {
int id;
}
class CustomIgniteBiPredicate implements IgniteBiPredicate> {
int searchKey;
public CustomIgniteBiPredicate(int searchKey) {
this.searchKey = searchKey;
}
public boolean apply(Integer key,
Hi,
You are right about the available options in terms of lack of flexibility
of approaching this problem.
How have you partitioned your data? You can probably have a local variable
specific to each node or compute thread (or maybe use an Atomic Type -
https://apacheignite.readme.io/docs/atomic-t
Hi Jose,
You can find an example usage of broadcastAsync here -
https://www.programcreek.com/java-api-examples/?class=org.apache.ignite.lang.IgniteFuture&method=listen
Regards,
RH
On Fri, Jan 25, 2019 at 6:40 AM joseheitor wrote:
> Thanks, Karun.
>
> From my interpretation of the Javadocs, I a
Correction - if you already have a specific key you use the affinityRun
On Fri, Jan 25, 2019 at 6:23 AM Karun Chand wrote:
> Hi Jose,
>
> You can probably use an IgniteClosure or an IgniteRunnable as you expect a
> return value from your compute job. An IgniteCallable may not be a
Hi Jose,
You can probably use an IgniteClosure or an IgniteRunnable as you expect a
return value from your compute job. An IgniteCallable may not be a good
idea as it does not return a value.
If you want your queries to go all nodes, a broadcast can be used. However,
if you already know specific n
Hi Weizhou,
Your ignite.log file shows this error -
[12:43:49,649][SEVERE][grid-nio-worker-tcp-comm-0-#33][TcpCommunicationSpi]
Failed to process selector key [ses=GridSelectorNioSessionImpl
Can you please provide more details about your query and definition?
Regards,
RH
On Thu, Jan 24, 2019 a
10 matches
Mail list logo
