Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 34F3D200C48 for ; Thu, 6 Apr 2017 12:07:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3388B160B84; Thu, 6 Apr 2017 10:07:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7B56D160B83 for ; Thu, 6 Apr 2017 12:07:44 +0200 (CEST) Received: (qmail 99925 invoked by uid 500); 6 Apr 2017 10:07:43 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 99916 invoked by uid 99); 6 Apr 2017 10:07:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2017 10:07:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 53571182390 for ; Thu, 6 Apr 2017 10:07:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 9vSh_d-wxIZe for ; Thu, 6 Apr 2017 10:07:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 46F0C5FB5A for ; Thu, 6 Apr 2017 10:07:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D77AFE0629 for ; Thu, 6 Apr 2017 10:07:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9649F24067 for ; Thu, 6 Apr 2017 10:07:41 +0000 (UTC) Date: Thu, 6 Apr 2017 10:07:41 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-4832) Service is deployed on client when service configuration is provided on startup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 06 Apr 2017 10:07:45 -0000 [ 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)