Igniters, may be I'm wrong, but in my opinion it slightly different functionality. Lifecycle is more like user functionality witch provide simple way to add additional behavior to cluster. I can implement interface LifecycleBean, do some logic (may be inject Ignite instance into it), add my implementation into class path and change xml configuration. I do no need coding something else.
Can I do it by simple events? For example, if I have one node without persistence, I can inject Ignite instance into my LifecycleBean, initiate cache, and load data into it using LifecycleEventType.AFTER_NODE_START. But if I have the cluster, I can't do it. Thanks. чт, 12 июл. 2018 г. в 15:25, Dmitriy Setrakyan <dsetrak...@apache.org>: > On Thu, Jul 12, 2018 at 3:22 PM, Yakov Zhdanov <yzhda...@apache.org> > wrote: > > > If events are working when grid is not active and adding/removing > listeners > > is also possible then I agree/ > > > > The events should be working. The cluster is not active, but the node is > started and should be able to fire events. > > AG, can you comment? > -- *Best regards, Sergey.*
