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
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
