You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Evgeniy Ignatiev <ye...@gmail.com> on 2017/04/03 13:26:03 UTC
Ignite may start more service instances per node than maxPerNodeCount
in case of manual redeploy
Hello.
Recently we discovered that if a service is configured in
IgniteConfiguration with e.g. maxPerNodeCount equal to 1 and totalCount
equal to 3, we start-up 2 Ignite nodes - then cancel the service after
some time and redeploy it with the same config as
ignite.services().deploy(...) - we observe more than instance of service
starting per node.
Here is a minimal code that demonstrates this issue:
https://github.com/YevIgn/ignite-services-bug - After the call to
ignite.services().deploy(...) - the output to console is "Started 3
services" while "Started 2 services" is expected as there are only two
nodes. This is with the Ignite 1.9.0.
Could you please look into it?
Re: Ignite may start more service instances per node than
maxPerNodeCount in case of manual redeploy
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi Evgeniy,
I've fixed the issue.
PFA a patch.
On Tue, Apr 4, 2017 at 12:23 AM, Andrey Mashenkov <
andrey.mashenkov@gmail.com> wrote:
> Hi Evgeniy,
>
> Looks like a bug. I've created a ticket [1].
> Seems, this reporoduced only when service deployment with dynamic
> approach. When Ignite starts with service configured - all looks fine for
> me.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4907
>
> On Mon, Apr 3, 2017 at 4:26 PM, Evgeniy Ignatiev <
> yevgeniy.ignatyev@gmail.com> wrote:
>
>> Hello.
>>
>> Recently we discovered that if a service is configured in
>> IgniteConfiguration with e.g. maxPerNodeCount equal to 1 and totalCount
>> equal to 3, we start-up 2 Ignite nodes - then cancel the service after some
>> time and redeploy it with the same config as ignite.services().deploy(...)
>> - we observe more than instance of service starting per node.
>>
>> Here is a minimal code that demonstrates this issue:
>> https://github.com/YevIgn/ignite-services-bug - After the call to
>> ignite.services().deploy(...) - the output to console is "Started 3
>> services" while "Started 2 services" is expected as there are only two
>> nodes. This is with the Ignite 1.9.0.
>>
>> Could you please look into it?
>>
>>
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
--
Best regards,
Andrey V. Mashenkov
Re: Ignite may start more service instances per node than
maxPerNodeCount in case of manual redeploy
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi Evgeniy,
Looks like a bug. I've created a ticket [1].
Seems, this reporoduced only when service deployment with dynamic approach.
When Ignite starts with service configured - all looks fine for me.
[1] https://issues.apache.org/jira/browse/IGNITE-4907
On Mon, Apr 3, 2017 at 4:26 PM, Evgeniy Ignatiev <
yevgeniy.ignatyev@gmail.com> wrote:
> Hello.
>
> Recently we discovered that if a service is configured in
> IgniteConfiguration with e.g. maxPerNodeCount equal to 1 and totalCount
> equal to 3, we start-up 2 Ignite nodes - then cancel the service after some
> time and redeploy it with the same config as ignite.services().deploy(...)
> - we observe more than instance of service starting per node.
>
> Here is a minimal code that demonstrates this issue:
> https://github.com/YevIgn/ignite-services-bug - After the call to
> ignite.services().deploy(...) - the output to console is "Started 3
> services" while "Started 2 services" is expected as there are only two
> nodes. This is with the Ignite 1.9.0.
>
> Could you please look into it?
>
>
>
--
Best regards,
Andrey V. Mashenkov