ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Platform updates
Date Fri, 04 Aug 2017 22:57:50 GMT
Hi Luqman,

It depends on what change you do exactly.

If a change is in data model, then it's best not to deploy these classes on
server nodes at all and take advantage of binary object. In this case you
don't even need to restart nodes, just start using new schema and it will be
picked up transparently.

If a change is in a compute task, you can use peer class loading [1] or
dynamic task deployment [2]. Again, no need to restart classes.

If a change is in service, then there is no built in mechanism for now. But
you can create a wrapper that will know class name of particular service
implementation and get class to create instance during deployment. When
service implementation change, you can use rolling upgrade technique.

[1] https://apacheignite.readme.io/docs/zero-deployment
[2] https://apacheignite.readme.io/docs/deployment-spi

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16012.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message