You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2015/09/28 14:28:04 UTC

[jira] [Updated] (IGNITE-170) A call of IgniteSet.iterator().next() can produce ClusterTopologyCheckedException on killing a node in topology.

     [ https://issues.apache.org/jira/browse/IGNITE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Shutak updated IGNITE-170:
--------------------------------
    Summary: A call of IgniteSet.iterator().next() can produce ClusterTopologyCheckedException on killing a node in topology.  (was: A call IgniteSet.iterator().next can produce exception on killing on node in topology.)

> A call of IgniteSet.iterator().next() can produce ClusterTopologyCheckedException on killing a node in topology.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-170
>                 URL: https://issues.apache.org/jira/browse/IGNITE-170
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Irina Vasilinets
>            Assignee: Semen Boikov
>
> h3. Original description.
> GridCachePartitionedAtomicSetFailoverSelfTest.testNodeRestart	fails sometimes.
> h3. Updated description.
> A call of the method next() on an IgniteSet iterator can produce 'javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Query execution failed' exception caused by 'ClusterTopologyCheckedException: Remote node has left topology' exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)