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 Wed, 24 Oct 2018 13:38:00 GMT

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

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

GitHub user ibessonov opened a pull request:

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

    IGNITE-9917 Write proper tests for start/stop client.

    

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

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

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

    https://github.com/apache/ignite/pull/5062.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 #5062
    
----
commit e3f0054d46a33333dd0ddd708c47274ec5ddebbf
Author: ibessonov <bessonov.ip@...>
Date:   2018-10-22T14:12:13Z

    IGNITE-9917 Start client test prototype that flacks all the time.

commit c018c5463935cd2b98c7323c87c9b928f5bb77e8
Author: ibessonov <bessonov.ip@...>
Date:   2018-10-24T13:27:42Z

    IGNITE-9917 Proper tests for start/stop client, not "muted" yes.

----


> 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
>
> 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