Hi dsetrakyan,
I checked the source again and found there is a customized Event sent out
with below code
org.apache.ignite.internal.processors.cluster.GridClusterSta
teProcessor#changeGlobalState0
I am not sure what you are referencing is this part? or still we need a
dedicated event for cluster status changes?
Thank you very much,
kcmvp
==============================
ChangeGlobalStateMessage msg = new ChangeGlobalStateMessage(start
edFut.requestId,
ctx.localNodeId(),
storedCfgs,
activate,
blt,
forceChangeBaselineTopology,
System.currentTimeMillis());
try {
if (log.isInfoEnabled())
U.log(log, "Sending " + prettyStr(activate) + " request
with BaselineTopology " + blt);
ctx.discovery().sendCustomEvent(msg);
====================================
Thanks,
Ken Cheng
On Tue, Jul 3, 2018 at 7:41 AM Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> Do we really not have events in Ignite for cluster activation?
>
> Alexey Goncharuk, can you please comment?
>
> D.
>
> On Mon, Jul 2, 2018 at 1:34 AM, kcheng.mvp <kcheng....@gmail.com> wrote:
>
> > Dear igniters,I am going to pick up
> > https://issues.apache.org/jira/browse/IGNITE-8376, and did some research
> > based on the comments.based on my understanding, if we want to know this
> > action is triggered by which way(rest, mbean, auto or visocmd) then we
> > need
> > to change the core method's signature.I am not sure my understanding is
> > correct or not. Can anybody help to clarify this? Thank you very much.By
> > the
> > way, I commented this in jira as well.Thanks youkcvmp
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
