Hi,
I want to receive the data even on one node. Can I add any set of commands
so that it can copy all partitions to active nodes when node left
(OR)
Can I make it is cache mode replicated and will it work?
Thanks & Regards,
Venkat
--
Sent from:
Hi,
That means that for a given partition to which given key is mapped, both
primary and backup partition nodes are offline. This cache ('users')
persistent and you are getting this exception when you have only one node
from baseline online. You have to get back both nodes online and call
Hi Team,
I have 3 node server mode cluster setup with Cache mode Partitioned with 1
backup. We are receiving above error as soon as 2 nodes left from cluster.
All 3 nodes are on baselinetopology.
Collection baselineNodes =
ignite.cluster().currentBaselineTopology();
hi Alex,
That was it. I read a little deeper into the doc and I wasn't setting the
baseline topology. I think I had it in my head that
ignite.cluster().active(true) set the topology. I see now that was
incorrect.
I just tested it and I'm good.
thanks a lot!!
--
Sent from:
Yes that is correct. I see the same exceptions when the cache is REPLICATED
with backups = 1 in my two node cluster.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
hi Alex,Sorry for the confusing comment. My baseline topology does not have
a client node. I was indeed referring to the current cluster topology in my
previous comment.
These ignite cluster nodes are programmed to come up and immediately run
ignite.cluster.active(true) but that is not
Yes that is correct. I see the same exceptions when the cache is
REPLICATED with backups = 1 in my two node cluster.
On Tue, Aug 21, 2018 at 12:37 PM akurbanov wrote:
> Hi,
>
> Do you see the same exception for a REPLICATED cache?
> And this exception also appears in two node setup with
Hi,
Do you see the same exception for a REPLICATED cache?
And this exception also appears in two node setup with backups = 1, when you
simply shut down one node, is that correct?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I think you are confusing the "current cluster topology" and the "baseline
topology" terms. Baseline topology cannot contain client nodes. Current
baseline topology can be printed or changed by "control.sh" script.
You can read more about baseline topology here: [1]
[1]:
This also occurs when I simply restart one of the ignite nodes without
changing the IP address. It has nothing to do with the upgrade process.
Here is my cacheconfiguration:
CacheConfiguration configuration = new
CacheConfiguration<>();configuration.setStatisticsEnabled(true);
Hi Alex,Yes, the baseline topology contains both the server nodes and the
client node. Everything is looks as I would expect including the IP
addresses.
A couple more notes:
when the nodes get restarted the IP addresses will disappear from the
baseline topology, then will come back. The IP
Hello,
Does baseline topology include both of your server nodes?
2018-08-21 3:32 GMT+03:00 scottmf :
> Hi, I'm seeing the errors below in my ignite cluster. This occurs
> consistently in my env when I apply a "rolling upgrade" where I take down
> one node at a time by updating them with a new
Hi, I'm seeing the errors below in my ignite cluster. This occurs
consistently in my env when I apply a "rolling upgrade" where I take down
one node at a time by updating them with a new jar file then start it up.
Once the node is up I then apply this to the next node and so on.
Notes:
The
13 matches
Mail list logo
