You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/06 10:07:41 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15958690#comment-15958690 ]
ASF GitHub Bot commented on IGNITE-4832:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1748
IGNITE-4832: Service is deployed on client when service configuration is provided on startup.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4832
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1748.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 #1748
----
----
> 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
> Assignee: Andrew Mashenkov
> Labels: newbie
> 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)