Ignition 8.3 Restart due to Enable Disable Modules

[csavaliya]

Hello,

I have noticed with Ignition 8.3 that when any module enabled/disabled, then it restarts the gateway which affects the clients. Is there any setting to avoid impact on perspective clients.

[Kevin.Herron]

It shouldn't be restarting the Ignition Gateway automatically, but it should require that you restart before the newly installed or upgraded module takes effect.

[csavaliya]

The gateway asks to restart gateway manually that will affects the concurrent clients. What if critical processes working and other side different module being installed for another project.

[andrew.budaiev]

Ignition 8.3 Needs restart after modules installs

It was a difficult decision to make when we decided to remove hot loading for 8.3.0, but ultimately we decided that we needed to do that. Hot loading causes all kinds of issues for the Java class loaders, and lead to the kinds of problems where you would need to restart running modules to clear up issues. By having the list of modules known at start up we avoid a lot of potential race conditions and instabilities.

[pturmel]

@csavaliya

What if critical processes working and other side different module being installed for another project.

Don't do that. Do your development in isolated development systems. Move development work to production systems during maintenance windows. To minimize downtime on critical systems, use redundant gateways in production, so you can perform maintenance on the inactive member of the pair.

Module hot-loading in v8.1 and before was always a risky business for production systems. (Been there, suffered for it.) v8.3 avoids a whole category of disasters by requiring deliberate deployment of modules.

Change your development behaviors or stay on v8.1.