Alexey,
Have a look at the 'PluginProvider' interface, if you implemented a
telemetry service as a plugin:
* plugin may be placed in the 'web-console' module;
* plugin is initialized at node startup and is stopped at node shutdown;
* plugin have access to all Ignite's internals through context;
*
Vyacheslav,
Thanks for detailed explanation.
As far as I see, we CAN support services on deactivated cluster, but it
does not seems a good idea from end user perspective.
I'm thinking that in my case (sending telemetry from cluster) I will go
another way.
--
Alexey Kuznetsov
Alexey,
If the question related only to Service Grid, I would say that it
shouldn't be difficult.
But there a lot of questions should be resolved before:
* public API is covered behind guards and user can't get services on
the inactive cluster (Ignite#services);
* service proxy's invocation proce
Denis,
I'm thinking that we could have services that could do something useful
even when cluster is deactivated.
For example, I'm investigating how I can implement a Web Agent as a cluster
singleton and I need that
Web Agent should be always "on-line" and send telemetry to Web Console.
Other user
Alex,
1. Why do you need an operational service if the cluster is deactivated (no
changes to data are allowed, right)?
2. That should be covered in the existing EIP
--
Denis
On Fri, Dec 7, 2018 at 6:20 AM Alexey Kuznetsov
wrote:
> Igniters,
>
> I would like to discuss how we can support follo
Igniters,
I would like to discuss how we can support following features for Service:
1) Made services work on deactivated cluster. What we need for that?
Introduce some flag on service configuration?
2) Auto start service after full cluster restart if service was started at
runtime.
Can we
