Hi,
Is there a particular reason for why replicated caches has their partition size
set to 512 by default?
I found this in
org.apache.ignite.internal.processors.cache.GridCacheUtils#initializeConfigDefaults(IgniteLogger,
CacheConfiguration, CacheObjectContext):V
if (cfg.getAffinity() =
Hey
I've created https://issues.apache.org/jira/browse/IGNITE-12058 for tracking
this.
Best regards
Niels Elkjær Ejrnæs
Software Developer R&D
From: Ilya Kasnacheev
Sent: 9. august 2019 18:54
To: user@ignite.apache.org
Subject: Re: AtomicReference issue with different userVersions
Hello!
Thi
I ran Multicast in the beginning as well, but the overlay network in Docker
Swarm does not support Multicast. So I had to drop it and use the
TcpDiscoveryVmIpFinder. Our containers register themselves in a shared
key-value database (etcd) upon startup and remove themselves on shutdown. We
then
Hello
We're testing out Ignite and are running them in Docker as well. It's a bit
tricky to get to work.
Keep in mind that referencing localhost inside a docker container is pointing
them against their internal address. Not the host address of your machine. So
that's why they aren't discovering
mall reproducer project for this behavior?
Regards,
--
Ilya Kasnacheev
чт, 8 авг. 2019 г. в 16:44, Niels Ejrnæs
mailto:niels.ejrn...@enghouse.com>>:
Hey all,
Am I wrong in assuming I can do this directly when running a client with a
different userVersion?
IgniteAtomicLong atomicLon
Hey all,
Am I wrong in assuming I can do this directly when running a client with a
different userVersion?
IgniteAtomicLong atomicLong = ignite.atomicLong("long", 0, false);
I get this Exception when running DeploymentMode CONTINUOUS and trying to
access either AtomicReferences or AtomicLongs
