2. If you want the Ignite cluster to be authoritative about caches, then
you should define them in the XML configuration or deploy your servers with
code which can look up the intended cache configurations and implement
them. If you have specific ideas how you would like to implement this,
maybe yo
2. I understood, You are talking about placing the cache in a persistent data
region and at the same time enabling the read-through, write-through caches
mode.
Thank you. This is, of course, a double penalty, but I’ll think about it and
test this mode.
5. It seems that Ignite has refocused on
For some cache the GetTimeTotal, PutTimeTotal , GetAllTime are only
updating on the client side , so I believe for those particular caches
these are client operations and there are some other cache where the
GetTimeTotal
n all can be seen at both client and server nodes so there i believe these
ope
Thanks Stephen,
2. «You can, actually, enable persistence and connect to a third-party data
store» - is this feature is not the same as using “external database”? coude
you please give the link to the documentation
5. Ignite seems to have to know which partitions are lost, and in theory it
doe
1. With a memory-only cluster, Ignite does not store any persistent
information. You'd need to save your table definitions somewhere yourself
2. If it saved data, it would be a database rather than an in-memory
data grid! You can, actually, enable persistence and connect to a
third-p
Most of the metrics are about the node you're talking about rather than the
cluster as a whole. When you're talking about a distributed system, is a
"get" a client or a server operation? A bit of both, right?
On Mon, 29 Jan 2024 at 14:05, Godfather wrote:
> Hi Community ,
> I have configured my
Hi All, I'm trying to use ignite (2.16) as an In-memory data grid (read-through
/ write-through caches), i.e. case described here
https://ignite.apache.org/use-cases/in-memory-data-grid.html
Several questions arose:
1. How is it recommended to store metadata for caches created dynamically
durin
