Hi,
Yep, that’s a bug. Daemon nodes (like the ones ignitevisorcmd starts) seem to
break baseline topology processing.
Filed https://issues.apache.org/jira/browse/IGNITE-8774.
Stan
From: szj
Sent: 9 июня 2018 г. 1:27
To: user@ignite.apache.org
Subject: Re: Ignite 2.5 nodes do not rejoin the
No, I definitely started with 2.5. I only took the trouble to try it later
with 2.4 to see that this problem did not exist there. 2.4 works fine in the
very same scenario.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, szj.
Could it be that you run 2 different version of Ignite? You have mentioned
that you used 2.4.
Ignite nodes should be the same version.
On Thu, Jun 7, 2018 at 8:36 PM, szj wrote:
> Hi
>
> I'm afraid I wiped Ignite off my servers already as this behaviour was a
> blocker to me. I only
Hi
I'm afraid I wiped Ignite off my servers already as this behaviour was a
blocker to me. I only needed a key value store able to replicate across
several datacenters across the globe (my use case involves very few writes)
and I'm now evaluating another product already.
I strongly suggest you tr
Hi,
What baseline topology does ./control.sh prints?
Is it possible, a node that out of baseline has started before baseline
node starts?
On Thu, Jun 7, 2018 at 9:54 AM, szj wrote:
> Well, it definitely does work in 2.4. Please notice that there needs to be
> ignitevisorcmd.sh involved to trigg
Well, it definitely does work in 2.4. Please notice that there needs to be
ignitevisorcmd.sh involved to trigger this bug (I didn't try with other
clients though). Here's what is printed by Java on the console:
[09:28:33]
[09:28:33] To start Console Management & Monitoring run
ignitevisorcmd.{sh|b
It's hard to guess what happened on your side without seeing error logs.
Ignite 2.5 passed QA cycles.
Share the logs.
--
Denis
On Tue, Jun 5, 2018 at 4:39 PM, szj wrote:
> I wiped Ignite 2.5 and tried 2.4. On a 2-node cluster I could restart each
> node back and forth without hindrance. I coul
That is not possible. The cluster was stripped down to 2 nodes and when
ignitevisorcmd.sh is not connected I can stop and start cluster nodes
freely. As soon as ignitevisorcmd.sh is connected to the grid on any of the
2 nodes at the time you stop one cluster node, that makes the stopped
cluster nod
HI,
Is it possible there are nodes out of baseline started ans node with
baseline is able to discover them?
On Wed, Jun 6, 2018 at 9:48 AM, szj wrote:
> I also tested an upgrade of the PoC 2-node cluster running Ignite 2.4 to
> 2.5.
> Both nodes shut down, upgraded, started on node1, started on
I also tested an upgrade of the PoC 2-node cluster running Ignite 2.4 to 2.5.
Both nodes shut down, upgraded, started on node1, started on node2, cluster
looking healthy with both nodes ONLINE. Then I shut down one of the nodes
with "kill -k -al" using batch ignitevisorcmd.sh. Trying to start it br
I wiped Ignite 2.5 and tried 2.4. On a 2-node cluster I could restart each
node back and forth without hindrance. I could even consider using 2.4 but
it lacks the authentication feature and also the rpm is built with all
contents world-writable which makes you wonder about the overall security of
t
Hi
I'm completely new to Ignite. I installed Ignite 2.5 and created a simple
3-node cluster (tried with 2 nodes too). I set a custom ConsistentID for
each node (same as the hostname). I also enabled *persistence* (does it
matter?). The cluster looks active and contains all 3 nodes. I print the
ba
12 matches
Mail list logo
