[ 
https://issues.apache.org/jira/browse/IGNITE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442676#comment-16442676
 ] 

ASF GitHub Bot commented on IGNITE-7968:
----------------------------------------

GitHub user pvinokurov opened a pull request:

    https://github.com/apache/ignite/pull/3868

    IGNITE-7968 IgniteAtomicSequence.incrementAndGet throws ClusterTopolo…

    …gyException: Failed to acquire lock for keys

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-7968

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3868.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 #3868
    
----
commit 692118e590ee66e2987eeb1b1f96024284bb52ae
Author: pvinokurov <vinokurov.pasha@...>
Date:   2018-04-18T15:19:14Z

    IGNITE-7968 IgniteAtomicSequence.incrementAndGet throws 
ClusterTopologyException: Failed to acquire lock for keys

----


> IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed 
> to acquire lock for keys
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-7968
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7968
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures
>    Affects Versions: 2.3, 2.4
>            Reporter: Pavel Vinokurov
>            Priority: Major
>             Fix For: 2.6
>
>         Attachments: AtomicSeqAndClusterTopologyReproducer.java
>
>
> When a primary node for a atomic sequnce has left cluster, 
> IgniteAtomicSequence.incrementAndGet  could throw ClusterTopologyException.
> The reproducer is attached. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to