Hello!
I recommend setting clientReconnectDisabled setting to true, and then do
your reconnects manually. I have heard of the issue where restarting a
client would interfere with data structures.
If you have a reproducer for this problem, I could review it and file a
ticket against Apache Ignite
Thanks.
We tried it outside the transaction when the ignite instance restarted with
EventType.EVT_CLIENT_NODE_RECONNECTED. However, it is hang at
igniteInstance.atomicLong().
// when the ignite instance restarted, it hangs here
userSeq = igniteInstance.atomicLong("userSeq", maxId,
Hello!
You need to do this outside of your transaction.
Regards,
Ilya.
--
Ilya Kasnacheev
сб, 12 сент. 2020 г. в 02:42, xmw45688 :
> Hi Ilya,
>
> Tried your suggestion, removing the userSeq field from the class. It still
> raise the same exception -
> org.apache.ignite.IgniteException:
Hi Ilya,
Tried your suggestion, removing the userSeq field from the class. It still
raise the same exception -
org.apache.ignite.IgniteException: Cannot start/stop cache within lock
or transaction.
The error is thrown when trying to get igniteInstance.atomicLong("userSeq",
maxId, true);
Hello!
If this is not too much of a slowdown, you can just remove the userSeq
field, and always use "igniteInstance.atomicLong("userSeq", maxId, true)"
in its place, to make sure you always hold a fresh one.
Regards,
--
Ilya Kasnacheev
пт, 28 авг. 2020 г. в 04:47, xmw45688 :
> How do we
How do we enable the persistence for this atomicLong? My understanding is
that atomicLong or atomicReference can't be persisted. Even if it can be
persisted, isn't next value reset and started from the initial value.
My issue is that the cached sequence was removed from Spring bean. How do I
Hi, as I remember AtomicInteger uses the default data region as storage, so
if you don't have persistence for it, then it will be lost after restart.
Try to enable persistence and check it again.
ср, 26 авг. 2020 г. в 18:08, xmw45688 :
> *USE CASE *- use IgniteAtomicLong for table sequence
*USE CASE *- use IgniteAtomicLong for table sequence generation (may not be
correct approach in a distributed environment).
*Ignite Server *(start Ignite as server mode) - apache-ignite-2.8.0.20190215
daily build
*Ignite Service* (start Ignite as client mode) - use Ignite Spring to
initialize the
