[
https://issues.apache.org/jira/browse/IGNITE-16375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482391#comment-17482391
]
Anton Vinogradov edited comment on IGNITE-16375 at 1/26/22, 10:46 AM:
----------------------------------------------------------------------
[~serge.korotkov]
It looks like *_startClientGrid(cfg)_* must also fail when a developer tries to
shoot its leg by setting client mode at more than one place.
Assertion that {{clientMode}} were not set before should de added.
The developer MUST be informed about the weak logic he implemented asap.
was (Author: av):
[~serge.korotkov]
It looks like *_ startClientGrid(cfg)_* must also fail when a developer tries
to shoot its leg by setting client mode at more than one place.
Assertion that {{clientMode}} were not set before should de added.
The developer MUST be informed about the weak logic he implemented asap.
> 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: Sergey Korotkov
> 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.1#820001)
