[
https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602057#comment-16602057
]
Ilya Kasnacheev commented on IGNITE-8987:
-----------------------------------------
Looks good to me!
The workflow is still not clear to me (why will this latch need to be reset) so
I suggest [~dpavlov] to chime in, take a look and merge hopefully.
> Ignite hangs during getting of atomic structure after autoactivation
> --------------------------------------------------------------------
>
> Key: IGNITE-8987
> URL: https://issues.apache.org/jira/browse/IGNITE-8987
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.4
> Reporter: Andrey Aleksandrov
> Assignee: Roman Guseinov
> Priority: Major
> Fix For: 2.7
>
> Attachments: reproducer.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
