Upgrading: Smart Grid to Smart Grid

If you are currently using a previous version of GigaSpaces XAPClosed GigaSpaces eXtreme Application Platform. Provides a powerful solution for data processing, launching, and running digital services, you can download the newest version from the download tab in the support portal.

Backwards Compatibility

For information about GigaSpaces' backwards compatibility policy, refer to the Product Life Cycle and End-of-Life Policy page.

Regarding the node, if a change

A change operation from a version including and older than 14.0.1 to a newer version might cause some issues in certain scenarios. See this Jira issue for more details.

Recommended Upgrade Steps

Follow this suggested upgrade procedure for performing a regular upgrade:

  1. First try to compile minimal code with the current maven artifacts (comment out hibernate & jetty integrations). Go to : Maven Doc.

  2. Change PUClosed This is the unit of packaging and deployment in the GigaSpaces Data Grid, and is essentially the main GigaSpaces service. The Processing Unit (PU) itself is typically deployed onto the Service Grid. When a Processing Unit is deployed, a Processing Unit instance is the actual runtime entity. xmls and remove version so version will be taken automatically from gs version running the PU. e.g., copy from blueprintClosed Java project templating framework provided by DIH for developers, a bueprint, or class, contains a set of attributes and behaviors that define an object..

  3. Change variables: Env Variables in setenv-overrides script if needed.

  4. If the manager was not used before use the gs-agent script to start the grid similar to the way it was done for the previous version.

  5. Fix the hibernate PUs to use the latest hibernate version.

  6. Fix web-PUs to use the current version of jetty, After all PUs are updated and all the code compiles try to deploy all PUs. Remember that the default service limit is 1 and start the GSCs accordingly (or change the default which is not recommended).

  7. Deploy the applications manually.

  8. Run your tests to validate behaviour.

  9. Move to use xap-manager instead of the deprecated gs-agent script, if you did not use xap-manager previously - see Manager Doc.

  10. Fix scripts to use the new CLI or new Rest APIClosed REpresentational State Transfer. Application Programming Interface An API, or application programming interface, is a set of rules that define how applications or devices can connect to and communicate with each other. A REST API is an API that conforms to the design principles of the REST, or representational state transfer architectural style..

  11. Add new features to improve performance and reduce memory footprint and monitoring.

  12. Retest and validate behaviour.

Flush Redo log to Disk Upon System Shutdown

This is only relevant when the redo log swap type is SQLite.

For more information, see Flush Redo Log to Disk



By default this is set to true which means the trailing zeros of big decimals are being dropped.  To change this, it needs to be set explicitly to false in both the client and server.

Hot Upgrade Overview

Hot Upgrade is required in order to perform changes without downtime, allowing the application users to keep working,

If there is no change in replication mechanism. GigaSpaces version hot upgrade is possible.

In order to upgrade to a new GigaSpacesversion without downtime, we have to allow a cluster with both new and old version to run simultaneously.

The hot upgrade feature is guaranteed only in the case of upgrading from the same major version, (e.g upgrade from 16.3 to 16.3.1 )

It is not guaranteed in case of different major versions.

For more information: Hot Upgrade