Hello!
"No".
What you can do, you can have a single shared persistent data region on
each node (you may even not put any caches in it) and also a large
persistent region on a subset (or just one) of nodes.
Then you need to specify node filter and data region name to those caches
you want to make
Yes it`s possible, but one data region can`t be mixed = persistent on one node
and in mem on another.
>Background on Use case: We have around 1 tasks that we want to run across
>ignite cluster. These tasks will be submitted by multiple independent client
>nodes. Each task will have a pri
I think you’d want to have at least two persistent nodes, or the loss of a
single node could take down your whole service.
> On 14 Jun 2021, at 15:51, Krish wrote:
>
> Background on Use case: We have around 1 tasks that we want to run across
> ignite cluster. These tasks will be submitted b
Background on Use case: We have around 1 tasks that we want to run across
ignite cluster. These tasks will be submitted by multiple independent client
nodes. Each task will have a priority and task key. Two tasks with the same
taskKey should not be running in parallel. Execution of all the task
Yes, but why? What’s the use case?
(Server nodes in your baseline topology will use the persistent store. Other
nodes will be memory-only.)
> On 14 Jun 2021, at 13:45, Krish wrote:
>
> Is it possible to have a cluster topology where native persistence is enabled
> only for one node and all oth
As long as you only have persistent caches on the persistent nodes it
should be fine, you cannot have a persistent cache on a non persistent
node as far as I am aware of.
On 2021-06-14 14:45, Krish wrote:
Is it possible to have a cluster topology where native persistence is enabled
only for on
Is it possible to have a cluster topology where native persistence is enabled
only for one node and all other nodes use in-memory cache store *without
*native persistence?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
