Hello Ognen, That's the exactly situation I'm trying to avoid.
One strategy that I'm planning to test is, for each physical cluster node, fire up a new ignite node with the updated code and the take down the old one. Effectively doing a rolling update of the cluster. But it's hard to tell what would be the effects in application runtime. One thing for sure, the new code must be backward compatible with the old one, or else, bad things will follow. Regards On Wed, May 27, 2015, 12:53 Ognen Duzlevski [via Apache Ignite Users] < [email protected]> wrote: > On Wed, May 27, 2015 at 9:31 AM, tcostasouza <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=417&i=0>> wrote: > >> Hello there, >> >> I'm building a POC infrastructure based on Ignite and I'm currently >> deciding >> if peer class loading in a production environment is a good idea or not. >> >> If it's not enabled, the suggested strategy is to copy the jars do every >> single onde. So, my question is if Ignite monitors it's libs folder and >> update it's classpath at runtime or do I need to restart the node. >> > > You can test this easily and as far as I can see it does not monitor the > ignite/lib for changes and it does not to automatic reloads. This is one > question that kind of screws it all up for production - imagine having a > large cluster that needs to be brought down and restarted after you copied > the jar around, each time you deploy a new version of an application. > > Ognen > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-ignite-users.70518.x6.nabble.com/About-peer-class-loading-tp416p417.html > To unsubscribe from About peer class loading, click here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=416&code=dGNvc3Rhc291emFAZ21haWwuY29tfDQxNnwtMTI3MjQ2NDcyNQ==> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/About-peer-class-loading-tp416p418.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
