Hello!
Can you please elaborate what happens if you try to restart a node in just
one cluster? How does it affect the other one?
Thanks,
--
Ilya Kasnacheev
вт, 25 авг. 2020 г. в 18:06, Nagarjun Ayyagari <
nagarjun.ayyag...@geodecapital.com>:
> Hi,
> Is there a solution to this? We are experie
Hi,
Is there a solution to this? We are experiencing a similar issue. We have
two separate clusters on the same physical server with 3 persistence enabled
nodes in each cluster. We are not able to restart nodes in one cluster
without restarting both the clusters.
Thanks
Nagarjun
--
Sent from: h
*If so
From: user@ignite.apache.org At: 12/30/19 18:35:35To: user@ignite.apache.org
Subject: Re: Isolating IgniteCache instances across JVMs on same machine by id
I will apply changes that you mentioned and see if this issue still occurs. If
not, I will attach logs.
From: user
te.apache.org
Subject: Re: Isolating IgniteCache instances across JVMs on same machine by id
Mitchell,
-For your first response, I just want to make sure I am clear how this works.
Say I have two different server nodes with IgniteInstanceName A and B. If both
nodes are part of the same cluster and bo
gt; To: Mitchell Rathbun (BLOOMBERG/ 731 LEX )
> Cc: user@ignite.apache.org
> Subject: Re: Isolating IgniteCache instances across JVMs on same machine
> by id
>
> Mitchell,
>
> -For your first response, I just want to make sure I am clear how this
> works. Say I have two different
e is no shared
directory for the cluster?
From: e.zhuravlev...@gmail.com At: 12/30/19 17:33:55To: Mitchell Rathbun
(BLOOMBERG/ 731 LEX )
Cc: user@ignite.apache.org
Subject: Re: Isolating IgniteCache instances across JVMs on same machine by id
Mitchell,
-For your first response, I just wan
gt; TcpCommunicationSpi? Or is one port for each fine?
>
> From: e.zhuravlev...@gmail.com At: 12/30/19 15:25:40
> To: Mitchell Rathbun (BLOOMBERG/ 731 LEX ) ,
> user@ignite.apache.org
> Subject: Re: Isolating IgniteCache instances across JVMs on same machine
> by id
>
> -
t for each fine?
From: e.zhuravlev...@gmail.com At: 12/30/19 15:25:40To: Mitchell Rathbun
(BLOOMBERG/ 731 LEX ) , user@ignite.apache.org
Subject: Re: Isolating IgniteCache instances across JVMs on same machine by id
-From your first response, it seems like the db id should be included in the
t; trying to join the baseline topology at the same time.
>
>
> From: user@ignite.apache.org At: 12/30/19 14:16:33
> To: Mitchell Rathbun (BLOOMBERG/ 731 LEX ) ,
> user@ignite.apache.org
> Subject: Re: Isolating IgniteCache instances across JVMs on same machine
> by id
>
>
time.
From: user@ignite.apache.org At: 12/30/19 14:16:33To: Mitchell Rathbun
(BLOOMBERG/ 731 LEX ) , user@ignite.apache.org
Subject: Re: Isolating IgniteCache instances across JVMs on same machine by id
Hi,
1. If the cache mode is local, why does IgniteCluster even come into play? All
that we
ghts on this?
>
> From: user@ignite.apache.org At: 12/18/19 19:55:47
> To: user@ignite.apache.org
> Cc: Anant Narayan (BLOOMBERG/ 731 LEX ) , Ranjith
> Lingamaneni (BLOOMBERG/ 731 LEX )
> Subject: Isolating IgniteCache instances across JVMs on same machine by id
>
> We hav
We have multiple different database instances for which we are looking into
using Ignite as a local caching layer. Each db has a unique id that we are
using as part of the IgniteInstanceName and for the WorkDirectory path. We are
running IgniteCache in Local mode with persistence enabled, as we
12 matches
Mail list logo
