GridGain Developers Hub

Deployment Units

In the Deployment Units tab you control the versions of dependencies you deploy to your cluster.

Code Deployment Page

Creating a new Deployment Unit

To create a new deployment unit, click Add Deployment Unit and specify the name for it in the subsequent dialog. The newly created deployment unit is stored as a draft, and is only stored in the frontend.

To add dependencies, click Add Artifact. In the subsequent dialog, you can specify where to procure artifacts from:

  • Uploaded Artifact - one of files uploaded in the Sources tab. These artifacts are stored locally.

  • Maven Artifact - the full Maven coordinate, for example org.apache.commons:commons-collections4:4.1;

  • URL - the direct URL of the dependency.

After you add all dependencies you need, click Deploy Version. Nebula will pass the list of dependencies to the cluster, and the deployment unit status will be changed to Downloading. When download is complete, the status will be changed to Available, and you can start your Distributed Computing tasks.

Updating Deployment Unit

Deployment units are immutable, so you need to create and deploy a new version each time you want to change dependencies. To do this:

  1. Click Clone. This will create a new version of your deployment unit in Draft state and increment version number.

  2. Change the dependencies you need. To remove or edit existing dependencies, click ⋮ and select Remove or Edit respectively.

  3. Click Deploy Version.

After you do this, Nebula will start downloading new dependencies. Old deployment unit version status will be changed to Retiring. It will have this status as long as there are jobs that use this class loader. When there are no jobs, the version will be Decommissioned.

Version History

Nebula stores all deployment unit versions and lists them in the Version history table. The table provides the following information:

Menu item Description


Version number.


Current version status. Possible version statuses:

  • Draft - A new version that has not been deployed yet.

  • Downloading - The version has been deployed and nodes are downloading dependencies.

  • Available - The version is currently deployed on the cluster.

  • Failed to Deploy - Failed to pass dependency information to the cluster. Try again.

  • Retiring - The version is outdated and is currently being replaced by the new version. Some tasks using the dependency are still running.

  • Decommissioned - The version is outdated and was replaced by a newer version.


The number of files in the deployment units.

Deployed at

Time and date of the deployment.

Reverting to an older version

If you want to switch to an older version (for example, one of the updated dependencies did not work as expected), you can deploy the previous version.

  • Open Version History.

  • Select the older version you need.

  • Click Clone and Deploy.

Nebula will create a new version and copy all dependencies from the version you chose.