...

Users may want to recompile and refresh classes without changing (remove, create) existing IgniteClassPath during development or hotfix.
Currently, we don't have plans to support this kind of scenario.

We assume the following user scenarios:

Deploy and run first version of application:

1. Pack jar files by regular procedures.
2. Create IgniteClassPath in running cluster.
3. Set name of classpath in app config.
4. Start Ignite client nodes or connect via thin clients.
5. Use classpath when starting jobs, services, etc.

Run second version of application in the same cluster:

1. Pack jar files by regular procedures.
2. Create second IgniteClassPath in running cluster.
3. Restart some instances of user application with the updated version in config.
4. Use updated classpath for new instances of application.
5. When tested update all application instances.

With this approach, we can update applications without any outages.

Discussion Links

// Links to discussions on the devlist, if applicable.

...