Denis,
I've just prepared PR [1] with a possible implementation that covers
p.1 from your list.
Please, have a look at it. Pay attention to the test, it demonstrates
manual services hot-redeployment via DeploymentSpi.
Is that what you mean?
[1] https://github.com/apache/ignite/pull/6060
On Tue
Vyacheslav,
I think, we can use IgniteConfiguration#deploymentSpi for tasks and
services.
Or we can add an analogous property.
Nik,
> 1. Is it possible to change the list of deployed resources in runtime via
built-in DeploymentSPI implementations?
> Can I add or remove jar to(from) class-path wi
In general, I think, we should work on the improvements in the following
order:
1. Cluster availability, when services are being updated. Should be solved
by usage of the DeploymentSpi
2. Service availability, when they are being updated. This one will
probably require introduction of new API meth
Hello, Denis.
Thank you for this discussion.
I have a few notes:
1. Is it possible to change the list of deployed resources in runtime via
built-in DeploymentSPI implementations?
Can I add or remove jar to(from) class-path without node(cluster) restart?
2. Can we update service dependencies via
Denis, thank you for driving of Service Grid's development!
Sounds like a good plan. Does it mean that a user will have to
register a classloader for service's class explicitly in case of using
the feature?
On Mon, Feb 4, 2019 at 4:38 PM Denis Mekhanikov wrote:
>
> Igniters,
>
> I'd like to star
