ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9917) Write proper tests for start/stop client.
Date Mon, 29 Oct 2018 13:59:00 GMT

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

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

Github user asfgit closed the pull request at:

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


> Write proper tests for start/stop client.
> -----------------------------------------
>
>                 Key: IGNITE-9917
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9917
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>             Fix For: 2.8
>
>
> Write proper tests for start/stop client. For now we only have "start client" tests that
don't actually check blocking on exchange in proper way.
> To correctly block client-only PME, it is necessary to block Discovery messages for node
join/left events from reaching some nodes in cluster. It will create a situation when nodes
have different AffinityTopologyVersion, but affinity assignments are still the same. After
https://issues.apache.org/jira/browse/IGNITE-9558 is done, all cache operations should work
successfully on such cluster.



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

Mime
View raw message