[
https://issues.apache.org/jira/browse/IGNITE-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-4907:
-------------------------------------
Description:
More than needed service instances can be started when service deployed
dynamicly.
For next service configuration all 3 instances will be started even if cluster
has 2 ignites nodes only:
cfg.setMaxPerNodeCount(1);
cfg.setTotalCount(3);
See for details:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html
was:
More than needed service instances can be started when service deployed
dynamicly.
For next service configuration all 3 instances will be started even if cluster
has 2 ignites nodes only:
cfg.setMaxPerNodeCount(1);
cfg.setTotalCount(3);
> Excessive service instances can be started with dynamic deployment.
> -------------------------------------------------------------------
>
> Key: IGNITE-4907
> URL: https://issues.apache.org/jira/browse/IGNITE-4907
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Affects Versions: 1.9
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Labels: user-experience
> Fix For: 2.0
>
> Attachments: ServiceDeploymentBug.java
>
>
> More than needed service instances can be started when service deployed
> dynamicly.
> For next service configuration all 3 instances will be started even if
> cluster has 2 ignites nodes only:
> cfg.setMaxPerNodeCount(1);
> cfg.setTotalCount(3);
> See for details:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
