I don't know if I even want to call an api to warm up memory. I am thinking,
we could have a setting like the below in config xml, this is userfriendly
and intention of the config file is very clear.
Bottomline: if ignite is used more often from disk, then it loses its value
from a performance sta
Denis, thanks for pointing out to that ticket.
Reopened that ticket proposing to reconsider the public API:
https://issues.apache.org/jira/browse/IGNITE-8873
Generally, I'm in doubts that IgniteCache.preloadPartition is the right API
from the usability standpoint. For instance, Mahesh do you unde
Hi Denis,
I tried removing Default_Region name property from config, still I see the
same behavior. But when I trigger load_cache process, and query the
cache(after a complete cluster restart) , I am getting the response.
Below is the Load_cache process.
*try* (Ignite ignite = Ignition.*start*(c
Correct and this is a pure practical issue. I can even imagine scenario
where you have a cluster and for compliance reasons visor is running in a
demilitarized zone.
And all I'm saying is that the visor CACHE command or any for that matter
should not hang waiting to connect to specific clients.
I
Sorry for the mix-up.
On Wed, Jun 19, 2019 at 2:35 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> This is the Apache Ignite user mailing list. For help with Apache Nifi
> you’ll need to engage with their community. See here:
>
> https://nifi.apache.org/mailing_lists.html
>
> Re
This is the Apache Ignite user mailing list. For help with Apache Nifi you’ll
need to engage with their community. See here:
https://nifi.apache.org/mailing_lists.html
Regards,
Stephen
> On 18 Jun 2019, at 17:02, Clay Teahouse wrote:
>
> https://nifi.apache.org/docs/nifi-docs/components/org.a
Denis,
Documentation for memory usage calculation covers another case (memory
usage by the node).
There is no ability (AFAIK) in released Ignite versions to calculate memory
used by a cache or cache group when persistence is disabled.
Dedicated data region can be used for some of the caches in som
Hi Taruk,
There is no such thing out of box. You can try to use
org.apache.ignite.Ignition#addListener and handle
org.apache.ignite.IgniteState#STOPPED_ON_SEGMENTATION state change
according to your needs.
Perhaps, if you can describe why do you need a specific handling then
the Community might s