You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2017/03/16 13:59:41 UTC

[jira] [Updated] (IGNITE-4832) Service is deployed on client when service configuration is provided on startup

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

Valentin Kulichenko updated IGNITE-4832:
----------------------------------------
    Attachment: ServiceConfigTest.java

> Service is deployed on client when service configuration is provided on startup
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-4832
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4832
>             Project: Ignite
>          Issue Type: Bug
>          Components: managed services
>    Affects Versions: 1.9
>            Reporter: Valentin Kulichenko
>             Fix For: 2.0
>
>         Attachments: ServiceConfigTest.java
>
>
> In case service configuration is provided on startup (i.e. as a part of {{IgniteConfiguration}}), the service can be deployed on the client node which is incorrect. Client nodes should be filtered out by default, like it's done in {{IgniteServices.deployXXX(..)}} methods.
> Test reproducing the behavior is attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)