Description
I investigate the use cases with autoactivation and creating of the IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it called after the last node from BLT was started.
Steps to reproduce:
First iteration:
Do next in one thread:
1)Start server 1
2)Start server 2
3)Activate the cluster
4)Create the IgniteAtomicSequence using next code:
IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence(
"TestName",
atomicConfiguration,
10,
true);
Second iteration:
1)Start server 1
2)Start server 2 (Autoactivation will be started)
3)Get the IgniteAtomicSequence using next code:
IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence(
"TestName",
10,
true); //could be false because TestName was already created in iteration 1
In this case, we hang in awaitInitialization() method in DataStructureProcessor.getAtomic() method.
In case if I added some sleep timeout between step 2 and 3 in the second iteration then everything was ok. Looks like we have some race here.
Attachments
Attachments
Issue Links
- Dependency
-
IGNITE-8023 Processors are incorrectly initialized if during a node's reconnection cluster changes its state
-
- Open
-
- links to
