ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eduard Shangareev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-170) A call of IgniteSet.iterator().next() can produce ClusterTopologyCheckedException on killing a node in topology.
Date Sat, 09 Jun 2018 17:17:00 GMT

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

Eduard Shangareev commented on IGNITE-170:
------------------------------------------

Hi, [~sboikov].

Do you plan to work with the ticket?

> 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
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> 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 (see the full stack
trace in comments). 



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

Mime
View raw message