Changelog

This section lists the changes that were made to GigaSpaces products for 15.5.x.

 

15.5.1

Features and Enhancements

  • GS-14242: ElasticGrid - improve life cycle of processing units
  • GS-14277: ElasticGrid - allow public access for AWS Cluster
  • GS-14267: ElasticGrid - use AWS credentials from the client host for node add/remove commands
  • GS-14263: ElasticGrid - Use --server=<node-ip> to communicate with cluster
  • GS-14264: ElasticGrid - ask for confirmation when running destroy command
  • GS-14251: Define liveness health check and cancel restarts in readiness health check for stateful service on ElasticGrid
  • GS-14258: Display a tooltip showing the index hits count in the object drill down page of the Ops Manager UI
  • GS-14225: Added support for scale up/down stateful pu without HA
  • GS-14247: Set logger level using environment variable or system property
  • GS-14246: Set metrics xml config file via GS_METRICS_CONFIG environment variable
  • GS-14245: Set metric sampler using environment variable or system property
  • GS-14205: Upgrade Oshi to 5.2.5
  • GS-14239: Change default pu memory to 512mb and managers default to 1024mb on ElasticGrid
  • GS-14236: Fix text overflow in GSCTL output to display all details including the token

Resolved Issues

    GS-14284: ElasticGrid - undeploy of a failed deployment leaks resources and causes error on redeploy
  • GS-14280: NullPointerException when failing to initialize connection to HSQLDB
  • GS-14278: ElasticGrid - scale out may hang when adding more than one partition with insufficient resources
  • GS-14279: ElasticGrid - node remove command may terminate nodes without draining them when removing multiple nodes
  • GS-14252: ElasticGrid - create cluster may fail when user-provided VPC/SG/subnet is in use
  • GS-14265: CPU utilization not consistently reported across platforms
  • GS-14261: Stateful blueprints fail to compile using Java 11 due to missing javax.annotation dependency
  • GS-14243: ElasticGrid - Creating AWS cluster using user-provided security group may fail when the inbound rules contain a rule for the client machine IP
  • GS-14074: After upgrading to 15 version, classNotFound exception due to usage of symbolic links
  • GS-14238: Retry policy used to connect a client to ZooKeeper elapses prematurely
  • GS-14223: Space remains in stopped state after network reconnection
  • GS-14257: Ops Manager UI displays an empty index
  • GS-14234: NullPointerException while running Explain Plan for Select Query that has id in Where clause
  • GS-14256: Change log level of SQLTransientConnectionException from SEVERE to WARNING
  • GS-14206: Oshi cause permanent WMI requests from XAP processes that are leading to a high CPU consumption
  • GS-14255: Ignore GS_PU_DYNAMIC_PARTITIONING environmental variable when deploying non-partitioned service
  • GS-14240: Create command might fail when using auto-generated subnet because of wrong availability zone choice
  • GS-14241: Grafana got 502 error in ElasticGrid caused by DNS resolution
  • GS-14080: Can't change port and IP in WEB UI
  • GS-14226: Change default disk size in ElasticGrid AWS
  • GS-14233: On Space shutdown, close ZooKeeper client's connection state listener
  • GS-14216: ElasticGrid support for Java 11 and later
  • GS-14228: After gsm restarted, exception [java.sql.SQLException: statement is closed] thrown for gsc
  • GS-14232: 'gsctl node add' command fails if a wrong component name was provided

Known Issues

For client version 14.0 or older, there is a possibility that the redo log will be corrupted and not available for system recovery.

This can only happen if all of the following conditions are true:

  • The client system is version 14.0 or older

  • AND the server-side system is a later release of 14.2 or higher

  • AND the old client did a Change operation.

  • AND the redo log exceeds RAM capacity and goes to the hard drive,.

15.5.0

Features and Enhancements

  • GS-14178: Service horizontal scale in Elastic Grid
  • GS-14177: Service vertical scale in Elastic Grid
  • GS-14170: Deploy/Undeploy Processing Units in ElasticGrid
  • GS-14199: Enhance InsightEdge JDBC driver to properly report catalog support
  • GS-14166: Add ability to deploy Processing Unit using the Ops Manager
  • GS-14180: Add ability to undeploy Processing Units using the Ops Manager
  • GS-14182: Add ability to run SQL Query with explain plan using the Ops Manager
  • GS-14157: Simplify Spring security integration
  • GS-14189: Add MongoDB as a built-in service for ElasticGrid
  • GS-14188: Support for @Repeatable meta-annotation
  • GS-14168: Improve performance of storing reported metrics to hsqldb
  • GS-14165: Support Compound Index from data connectivity
  • GS-14154: New REST API for vertical scaling of a service for ElasticGrid and Kubernetes
  • GS-14160: On-demand service scale with multiple partitions using Ops Manager with Kubernetes
  • GS-14163: View log of Service instance in Ops Manager
  • GS-14079: Dynamically scale in/out a Space partition
  • GS-14169: GSCTL as REST Service
  • GS-14175: Add new CLI command for vertical scaling of a service for ElasticGrid and Kubernetes
  • GS-14167: Set index type and edit existing index in data connectivity view
  • GS-14114: Volume support for services persistence for ElasticGrid
  • GS-14100: Heap size report in Ops Manager
  • GS-14131: On-demand single partition vertical scale in Ops Manager for ElasticGrid and Kubernetes
  • GS-14143: Enhance data connectivity to support tables with multiple column primary keys
  • GS-14161: Custom roles for in-memory Spring security configuration
  • GS-14155: Service To service continuous data transfer
  • GS-14159: Allow configuring Jetty's request header size
  • GS-14156: Session cookies for GigaSpaces web-based tools are now unique
  • GS-14141: Enhance mirror service with Apache Kafka
  • GS-14148: Add option for auto revert on vertical scale in Kubernetes
  • GS-14151: Start ElasticGrid cluster with security
  • GS-14130: Show index hits in Ops Manager
  • GS-14123: TDVT – Update dialect, connection string and utils for Tableau JDBC connector
  • GS-14122: Start ElasticGrid cluster with TLS enabled
  • GS-14139: Secure Ops Manager with authentication
  • GS-14133: Allow to predefine data sources for Ops Manager
  • GS-14132: Automatically select optimal iterator type for embedded/remote space
  • GS-14125: Report and display data type index hits in Grafana
  • GS-14105: Allow duplicate UIDs in single writeMultiple on InsightEdge w/RocksDB
  • GS-14126: Enhance QueryCache to log a warning when cache is full
  • GS-14111: Upgrade Nomad from 0.10.1 to 0.11.2 and Consul from 1.6.1 to 1.7.3
  • GS-14104: Adding support for IAM role binding to an EC2 instance
  • GS-14085: Expose instances log in Ops Manager
  • GS-14077: Improved performance using getLastStatistics instead of getStatistics
  • GS-14119: Optimize shortest-index selection to speed up query execution
  • GS-14214: Data-connectivity support for Oracle and PostgreSQL

Resolved Issues

  • GS-14088: Add support in data-connectivity for database tables with an auto-generated ID column
  • GS-14179: Error creating bean specified in LDAP Spring security configuration file
  • GS-14145: Override metrics DB port using com.gs.ui.metrics.db.port system property
  • GS-14135: Select shortest index for known and unknown sizes
  • GS-14144: Explain plan shows unusable index as selected for matching
  • GS-14121: Configure amount of time to block on a read call from socket
  • GS-14117: The 'pu run' and 'space run' CLI commands fail when Java 11 is used
  • GS-14112: Space Iterator of type CURSOR returns empty results with super type queries
  • GS-14109: After a network reconnect a pending instance might be discarded and not monitored for liveness
  • GS-14096: Failing validation phase couldn't destroy the cluster and its dynamic resources on AWS mode
  • GS-14091: Destroy terminates all instances related to the vpc provided by the user
  • GS-14083: When there is a dash in the space name, the Object type drill down does not work

Known Issues

  • GS-14215: Edge case when the deployment of a service failed and the job will remain in Nomad
  • GS-14206: Oshi cause permanent WMI requests from XAP processes that are leading to a high CPU consumption
  • GS-14206: Tableau 2020.02 (or later) support requires disabling custom load.

For client version 14.0 or older, there is a possibility that the redo log will be corrupted and not available for system recovery.

This can only happen if all of the following conditions are true:

  • The client system is version 14.0 or older

  • AND the server-side system is a later release of 14.2 or higher

  • AND the old client did a Change operation.

  • AND the redo log exceeds RAM capacity and goes to the hard drive,.

 

The complete list of changes is also available in Jira.