BigMemory Max 4.3.5 | Upgrade and Migration Guide | Upgrading from 3.7 or 4.0 | Summary of Changes from 3.7 to 4.0
 
Summary of Changes from 3.7 to 4.0
Area of Change
Change from 3.7 to 4.0
TSA Operation
TSA Disk Usage
*Data held in memory only.
TSA Configuration
*No more DSO.
*offheap required.
TSA Monitoring
Terracotta Management Console (TMC) replaces the Dev Console.
TSA Security
Interoperability
BigMemory Hadoop Connector.
API
Tier Configuration
MaxEntriesInCache replaces MaxElementsOnDisk.
Pinning
*Key-level pinning removed.
*PinningConfiguration.Store#LOCALHEAP removed.
Statistics
Continuous Uptime for 4.0 and Higher
Improvements to provide continuous availability of data include:
*Support for multiple mirrors in mirror groups, with better utilization of extra mirrors.
*Flexibility in server startup sequencing. A mirror server can start up first during a cluster restart, and it will wait for the active server.
*Multi-stripe backup capability.
*Optimizations to bulk loading.
*Performance improvements for data access on rejoin.
*No more Oracle Berkeley DB, enabling in-memory data to be ready for use much more quickly after any planned or unplanned restart.
Simplified Configuration of tc-config.xml for 4.0 and Higher
The tc-config.xml has extensive changes from version 3.7:
*The <mirror-group> element can now wrap <server> configuration blocks, eliminating the need to repeat the setup of <server> information.
*<dso-port> is renamed to <tsa-port>, and <l2-group-port> is renamed to <tsa-group-port>.
*<client-reconnect-window>, <garbage-collection> (DGC), and <restartable> settings are now global for all servers.
*The <data> element specifies where to store data files used for the Fast Restartability feature.
*The <clients> section now has one setting, <logs>.
*<security> is a new configuration block for setting up authorization/authentication and SSL.
*<dso>, <system>, <statistics>, <persistence>, and <ha> (and, unless otherwise noted, any sub-elements) have been removed.
See the BigMemory Max Administrator Guide for a complete listing and definitions of configuration elements.
Security Changes for 4.0 and Higher
*HTTP authentication no longer supported.
*Security is enabled at the Terracotta Management Server (TMS) level, and so the server scripts only need the following when security is enabled:
*https TMS URL
*username and password
*Keychain entries are required for Terracotta clients, servers, and the Terracotta Management Console (TMC). By default, the keychain script that creates Terracotta keychain files uses an obfuscation scheme to protect passwords.
*Active Directory (AD) and Lightweight Directory Access Protocol (LDAP) support is available for Terracotta servers (see "Using LDAP or Active Directory for Authentication in the document BigMemory Max Security Guide).
*Custom SecretProvider is available for Terracotta clients (see document BigMemory Max Security Guide).
Statistics Changes for 4.0 and Higher
Beginning in version 4.0, statistics are no longer explicitly enabled or disabled via the ehcache.xml configuration file. The core counters for statistics are always enabled, but they have no impact on performance.
If you call for a statistic, via the TMC or programmatically, the various components of the statistic (latency, avg, min, max, history) will start being kept. As long as the statistic continues to be sampled within a defined amount of time, that statistic will be kept active.
Note that this is done on a per-statistic basis, so the overhead can vary depending on how many statistics are being sampled.

Copyright © 2010 - 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release