...

1. Send command to random server node.
2. Update ICP status in metastorage.
3. Return result to the user.
4. When some code tries to start on top of ICP Ignite must check ICP status and throw exception if status not READY.
5. Each server node must track usage count for ICP:
   1. When some user code starts - increase usageCount.
   2. decrease usageCount on finish.
6. Eventually usageCount will become zero. Node must clean local resources then.

unsafe remove

1. Send command to all server node.
2. Remove ICP status in metastorage.
3. Remove all files from local disk.
4. Return result to the user.

Risks and Assumptions

We assume that p2p and deployment SPI will be removed from Ignite.

...

1. https://spark.apache.org/docs/latest/submitting-applications.html
2. https://tomcat.apache.org/tomcat-11.0-doc/deployer-howto.html
3. https://nightlies.apache.org/flink/flink-docs-stable/docs/ops/debugging/debugging_classloading/
4. https://nightlies.apache.org/flink/flink-docs-release-2.2/docs/ops/rest_api/
5. IEP-103: Code Deployment

Tickets