ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-170) A call IgniteSet.iterator().next can produce exception on killing on node in topology.
Date Mon, 28 Sep 2015 12:27:04 GMT

     [ 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 IgniteSet.iterator().next can produce exception on killing on node in
topology.  (was: GridCachePartitionedAtomicSetFailoverSelfTest#testNodeRestart fails with
'ClusterTopologyCheckedException: Remote node has left topology')

> A call IgniteSet.iterator().next can produce exception on killing on 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)

Mime
View raw message