Versions Compared

Old Version 4

changes.mady.by.user Unknown User (nizhikov)

Saved on

compared with

New Version 5

changes.mady.by.user Unknown User (nizhikov)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • control.sh command to create/remove/list resources.
  • control.sh command to register class path from server node resource.
    In strict environments it often prohibited for process to modify it's code (jars).
    So, regular flow with the "Ignite, please deploy files from the local disk to cluster" not working.
    We must provide a way to register and validate IgniteClassPath from server node local disks. 
  • system view to list available instances.

Examples:

Code Block
$ ./control.sh --ignite-classpath create --name superapp_v1 --files ./my-app-v1.jar,./grpc-context-1.19.0.jar,./error_prone_annotations-2.1.3.jar
$ ./control.sh --ignite-classpath remove --name superapp_v0
$ ./control.sh --system-view IGNITE_CLASSPATHES
Code Block
Ignite ignite = ...

IgniteCompute compute = ignite.compute(ignite.cluster().forServers());

// Running compute with the provided jars.
compute.withClasspath("superapp_v1").() -> {
    MyLibClass libClass = MyLibClass.getInstance();
    // other code.
};


ServiceConfiguration serviceCfg = new ServiceConfiguration();

serviceCfg.setName("mysuperappService_v1");
serviceCfg.setService(new MySuperappServiceImpl());
serviceCfg.setIgniteClasspath("mysuperapp_v1");

ignite.services().deploy(serviceCfg);



Other systems approach:

Apache Spark

...