Hello Ankit,
I'm not an expert in docker, but for me it looks like you have a problem
with overall cache persistence (not only with AtomicSequence), could you
try to put some values into cache and check their availability after the
restart?
пт, 28 сент. 2018 г. в 23:45, abatra :
> To give more
Ankit,
> 1. I run two nodes in the cluster.
I checked 2 nodes cluster restart (simultaneously, 2 processes on same
machine) with the same result - after restart the "current" value !=
"initial" value.
> 2. I restart the entire node and hence the server gets restarted.
I gave this example only
Ankit,
I tried test your example with the following code:
configure();
System.out.println("Initial value: " + getCurrentValue("sequence"));
for (int i = 0; i < 10_000; i++)
incrementAndGet("sequence");
stop();
configure();
System.out.println("Value after restart: " +
Ankit,
I checked sequence and atomic on Ignite 2.6 with the following code:
try (Ignite ignite = Ignition.start("example-persistent-store.xml")) {
ignite.active(true);
IgniteAtomicSequence seq = ignite.atomicSequence("sequence", 0, true);
IgniteAtomicLong atomic =
nderstand, question is about IgniteAtomicSequence?
> We fixed IgniteSet to be persisted and recovered properly.
>
> Pavel Pereslegin,
>
> Could you please check whether we have the same issue with
> IgniteAtomicSequence?
>
> сб, 22 сент. 2018 г. в 4:17, Denis Magda :
>
&g
Hello, BIren.
I think the impact on performance is minimal, but I don't have exact figures.
2017-11-05 22:05 GMT+03:00 Biren :
> Thank you Pavel!!. I have not enabled statistics. Do you know what would be
> performance impact on enabling it?
>
> -Biren
>
>
>
> --
>
Hello, Biren.
Did you enable statistics in the cache configuration?
2017-11-04 2:43 GMT+03:00 Biren :
> We are investigating performance issue on our cluster of 2 nodes. We are
> trying to understand time it takes to get or put a cache entry from/to the
> cache. We