You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by the_palakkaran <ji...@suntecsbs.com> on 2018/10/18 10:13:40 UTC

Is it possible to avoid redeployment of an Ignite service n a cluster even if the node bound to it gets down?

Hi,

I have a cache loading service in an ignite cluster. Since cache loading is
expected to be a one time activity, is it possible to avoid a redeployment
if the node bound to it gets down? If it gets deployed again, it will load
cache again, which is not expected.

PS: I have a work around to keep a cache for marking loading complete. I
just want to know if there is a simpler solution.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Is it possible to avoid redeployment of an Ignite service n a cluster even if the node bound to it gets down?

Posted by Ilya Kasnacheev <il...@gmail.com>.

Hello!

I think that you should use compute or lifecycle listener in place of
service for such scenario.

Service is something that needs to be deployed continuously.

Regards,
-- 
Ilya Kasnacheev


чт, 18 окт. 2018 г. в 13:13, the_palakkaran <ji...@suntecsbs.com>:

> Hi,
>
> I have a cache loading service in an ignite cluster. Since cache loading is
> expected to be a one time activity, is it possible to avoid a redeployment
> if the node bound to it gets down? If it gets deployed again, it will load
> cache again, which is not expected.
>
> PS: I have a work around to keep a cache for marking loading complete. I
> just want to know if there is a simpler solution.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>