[IGNITE-4832] Service is deployed on client when service configuration is provided on startup

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9
• Fix Version/s: 2.0
• Component/s: managed services
• Labels: newbie
• Assignee: Andrey Mashenkov
• Reporter: Valentin Kulichenko
• Created: 16/Mar/17 13:58
• Updated: 07/Apr/17 09:56
• Resolved: 07/Apr/17 09:41

Description

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.

Issue Links

• links to: GitHub Pull Request #1748
• links to: Upsource review IGNT-CR-161