You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/31 12:24:00 UTC
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of
atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670018#comment-16670018 ]
ASF GitHub Bot commented on IGNITE-8987:
----------------------------------------
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5222
IGNITE-8987: Fix testSequenceAfterAutoactivation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8987-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5222.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5222
----
commit 1caaeb65878f13cfb1fdd56e26d8a11cdda83652
Author: ipavlukhin <vo...@...>
Date: 2018-10-31T12:21:20Z
access atomicSequence on auto-activating cluster with retries
----
> 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)