You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2022/09/29 11:33:00 UTC

[jira] [Assigned] (IGNITE-16375) GridAbstractTest.startClientGrid() method does not guarantee that started node will be the client

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

Yury Gerzhedovich reassigned IGNITE-16375:
------------------------------------------

    Assignee: Yury Gerzhedovich  (was: Sergey Korotkov)

> GridAbstractTest.startClientGrid() method does not guarantee that started node will be the client
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-16375
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16375
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Anton Vinogradov
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: newbie
>         Attachments: Client_node_start_failed_reproducer.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If {{cfg.setClientMode(false)}} was applied to the Ignite configuration, {{GridAbstractTest.startClientGrid()}} will start the server node, while client node is expected according to the method name and JavaDoc.
> {noformat}
> Starts new client grid with given index.
> {noformat}
> {{GridAbstractTest.startClientGrid()}} should start client node even when {{cfg.setClientMode(false)}} is set or throw an exception (preferred). 
> See reproducer at  [^Client_node_start_failed_reproducer.patch] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)